-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Cache and Eviction, Checkpoints
-
None
-
Storage Engines
-
252.97
-
None
-
None
At the moment, when checkpoint reconciles a page it will always leave the in-memory page in place with the original set of updates. It can often mark the page clean.
Those pages with updates that just hang out cause the cache to be in a less optimal state.
We should add code that will attempt to swap the page with updates, with an equivalent disk-image that was just generated by reconciliation. That process would be equivalent to scrub-evicting a page that was dirty. It requires that checkpoint tries to get exclusive access to the page, if it succeeds it will proceed with the scrub eviction.
- is related to
-
WT-16244 Skip writing the leaf page if one-to-one page replacement reconciliation doesn't make any progress in disagg
-
- Closed
-