Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Incomplete
-
None
-
None
-
None
-
None
Description
This behavior is described in the BT paper. Years ago I had a go at it but at the time it slowed flushing significantly – and IIRC we had no barriers on writes when the memory pressue was high – so it brought on OOMEs... so punted on it. Its time to consider this feature again.
Would we always do it? Maybe not if its a close? If a close we want stuff to run quickly so we should skip the merge. But any other time, we should do it?