-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Compaction
-
None
-
Storage Engines
-
5
-
StorEng - Defined Pipeline
The investigation should be done for background and foreground compaction. It would be best to come up with a solution that could benefit other subsystems that should have a different behaviour whenever there is cache pressure.
Background compaction
Background compaction is throttled here, if dirty/clean eviction is needed, we don't proceed with compaction and loop over.
*Foreground compaction
*When compaction is happening (note that this code is triggered from background compaction as well), there is an eviction check here. During that check, it is possible for the thread to help with eviction if there is cache pressure. Note that this is a recent change from WT-13216 which allows a compaction thread to help with eviction. Inside this check, if we have reached one of the trigger thresholds and if we have, we proceed with eviction.
The questions are:
- Do we want to wait for the thresholds to be reached before helping with eviction?
- Do we want to throttle compaction using different thresholds?
- related to
-
WT-13216 Assess the use of cache eviction check in compact
-
- Closed
-