Production implementation phase T4 (~4 days). Begins after both T2 and T3 are complete.
Changes:
- __wt_evict_file(): harden WT_SYNC_BULK_FLUSH case to production quality
- Production __wt_bulk_flush(): wire T2 (suspend/resume) and T3 (rightmost path rebuild) together
- _curbulk_insert_row(): threshold triggers production _wt_bulk_flush()
Test: Python smoke test — single flush end-to-end on row-store, final tree is logically correct
Depends on: WT-17213 (T2), WT-17214 (T3)
Next: T5, T6 (can run in parallel)
- is related to
-
WT-17213 Bulk insert flush — implement production reconcile suspend/resume
-
- Needs Scheduling
-
-
WT-17214 Bulk insert flush — implement production rightmost path rebuild
-
- Needs Scheduling
-
- related to
-
WT-17216 Bulk insert flush — add functional test suite (Python suite)
-
- Needs Scheduling
-
-
WT-17217 Bulk insert flush — add crash recovery tests
-
- Needs Scheduling
-
-
WT-17218 Bulk insert flush — cppsuite stress test: concurrent bulk loads with background checkpoint
-
- Needs Scheduling
-
-
WT-17219 Bulk insert flush — cppsuite stress test: crash injection during flush
-
- Needs Scheduling
-
-
WT-17220 Bulk insert flush — cppsuite stress test: memory pressure
-
- Needs Scheduling
-
-
WT-17221 Bulk insert flush — scale test: large table load and O(1) memory verification
-
- Needs Scheduling
-
-
WT-17222 Bulk insert flush — performance benchmarking: throughput and flush overhead
-
- Needs Scheduling
-