-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Cache and Eviction
-
Security Level: Public (Available to anyone on the web)
-
Storage Engines, Storage Engines - Transactions
-
8,386.476
-
None
-
None
-
0
WiredTiger has added a mode that allows for enabling precise checkpoints. When precise checkpoints are enabled, content newer than the stable timestamp (or checkpoint timestamp when a checkpoint is running) cannot be evicted - it needs to be retained in the cache.
That means that any dirty page that is reconciled while it has content newer than the checkpoint timestamp needs to be retained in cache, and the changes that were too new to include in a reconciliation are restored in the cache (this is called update-restore eviction).
We should add an eviction selection heuristic that avoids evicting pages with updates newer than the checkpoint timestamp, when precise checkpoints are enabled as long as there isn't an excess of cache pressure.
- is related to
-
-
- Closed
-
- related to
-
WT-15110 Assertion failed: "The page checkpoint id doesn't match the current checkpoint id"
-
- Open
-
-
WT-15119 Dynamically tune WT_EVICT_MODIFY_COUNT_MIN based on workload characteristics
-
- Open
-
-
-
- Closed
-
-
-
- Closed
-