View Revisions: Issue #7099
| Summary | 0007099: Optimize Full Load by sending index definitions before the Finalize batch is sent | ||
|---|---|---|---|
| Revision | 2025-10-22 17:27 by mdrouard | ||
| Description | The fix for issue 0007098 will cause Symmetric to always sort by FK order. This ticket is being opened to discuss when you would not want to sort by FK order, and how to speed up initial loads |
||
| Revision | 2025-10-22 17:44 by mdrouard | ||
| Description | The fix for issue 0007098 will cause Symmetric to always sort by FK order. This ticket is being opened to discuss when you would not want to sort by FK order, and how to speed up initial loads Could check the order if the FK references when running Sync Triggers |
||
| Revision | 2025-10-22 18:05 by mdrouard | ||
| Description | The fix for issue 0007098 will cause Symmetric to always sort by FK order. This ticket is being opened to discuss when you would not want to sort by FK order, and how to speed up initial loads Could check the order if the FK references when running Sync Triggers 2 pass idea After loading data for a given table then load the index for the given table with the data as a data batch. Load data for A, add index for A Load Data for B, add index for B and so on... Then Finalize Add the FK references To A,B,... |
||
| Revision | 2025-10-22 18:29 by pbelov | ||
| Description | The fix for issue 0007098 forced full loads to always sort tables by FK order, which slows the initial processing down. Sometimes this slowdown is significant! To optimize a Full Load SymmetricDS could send index definitions before the Finalize batch is sent, right after all load-related data batches are sent. |
||