# Parallel Load 2026-05-18

4-route parallel TiDB load plan for the existing `full_phase1` snapshot.

Rules:

- Each worker owns a disjoint object set.
- Do not run two workers that write the same table.
- All workers point at the same snapshot directory.
- Summary files are isolated per worker.
- Failed chunk artifacts still land under:
  - `<snapshot-dir>/_load_failures/<ObjectName>/`
  - This is safe because object ownership is disjoint across workers.

Routes:

1. `worker_core`
   - `UserRole`
   - `RecordType`
   - `Account`
   - `Contact`
   - `Campaign`
   - `Opportunity`
2. `worker_activity`
   - `Lead`
   - `CampaignMember`
   - `Task`
   - `Event`
   - `org__c`
   - `invoice_collection__c`
3. `worker_quote_pricing`
   - `Quote`
   - `Contract`
   - `Product2`
   - `Pricebook2`
   - `PricebookEntry`
4. `worker_content`
   - `ContentDocument`
   - `ContentVersion`
   - `ContentDocumentLink`

Suggested execution order:

1. start `worker_core`
2. start `worker_activity`
3. wait 1-2 minutes
4. start `worker_quote_pricing`
5. start `worker_content`

This keeps the most dependency-heavy route (`worker_quote_pricing`) slightly
behind the core route without forcing a fully serial load.