-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2026-11-23
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When the filling buffer's usage exceeds half of maxMemoryUsageBytes, NoLimitSorter sorts it and calls Spiller::beginSpill() before swapping buffers, so the sorted buffer's keys are written while the other buffer receives keys; beginSpill fires SpillCallbacks::onSpillBegin. The Sorter base's single pool member becomes an array so the second buffer's pool can be engaged at the first incremental spill, and supportsIncrementalSpilling() is constant per spiller type, so file-backed sorters keep the whole-buffer spill.
At this stage the crossing still writes the whole sorted buffer at once, so throughput is unchanged from master; pacing and the resume-position capture arrive in SERVER-139274.
- is related to
-
SERVER-139274 Pace incremental spilling with byte-count debt
-
- In Progress
-
- split from
-
SERVER-138779 Give NoLimitSorter two swapping buffers for incremental spilling
-
- In Code Review
-