-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Cache and Eviction
-
Security Level: Public (Available to anyone on the web)
-
Storage Engines - Transactions
-
6,162.866
-
SE Transactions - 2026-01-30, SE Transactions - 2026-02-13
-
5
We’ve observed cases where the eviction candidate queue is frequently empty or underfilled, particularly during update-only eviction WT-15538. Eviction walks are active but eviction makes little progress because too few candidates are queued.
Eviction intentionally queues only a percentage of potential candidates in order to reserve space for urgent eviction. This is counterproductive when the queue is often empty and eviction is already under pressure.
This ticket is to test a change for when eviction is operating in update-only mode and the candidate queue is consistently empty when topping up, allow eviction to queue more candidates.
- causes
-
WT-16678 Performance regression in update/read operation times in perf-cache_update_trigger tasks
-
- Closed
-
- is related to
-
WT-15538 Investigate slow eviction behavior when updates ratio is high
-
- Open
-
-
WT-16745 Investigate eviction queue usage when the queue is frequently empty
-
- Open
-
- related to
-
WT-16745 Investigate eviction queue usage when the queue is frequently empty
-
- Open
-
-
WT-16722 Cache performance fluctuate investigation
-
- Backlog
-
-
WT-17236 Per-btree dirty-index ring with adaptive drain throttling for eviction
-
- Open
-