-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2026-08-31, Storage Execution 2026-09-14, Storage Execution 2026-10-12, Storage Execution 2026-11-09, Storage Execution 2026-11-23
-
None
-
None
-
None
-
None
-
None
-
None
-
None
During index builds, the sorter can accumulate significant amount of index keys in memory (default 200MB) before spilling, resulting in a workload where we have large bursts of writes that can be fairly spaced out. This can interact poorly with flow control, which can kick in due to standby replication lag.
We should investigate if we can smooth out this workload with some form of incremental spilling, with the goal of getting better performance by avoiding flow control kicking in due to standby replication lag.
- is duplicated by
-
SERVER-132685 Incrementally spill sorter data when using container-based spilling
-
- Closed
-
- related to
-
SERVER-139235 Add incremental_sorter_spilling.js end-to-end jstest
-
- In Progress
-
- split to
-
SERVER-138780 Add resumable index build coverage for incremental spilling
-
- Open
-
-
SERVER-138781 Run sys-perf for the incremental sorter spilling stack before merge
-
- Open
-
-
SERVER-138779 Give NoLimitSorter two swapping buffers for incremental spilling
-
- In Code Review
-
-
SERVER-138778 Add incremental spilling support to Spiller and ContainerBasedSpiller
-
- Closed
-