Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Minor - P4
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: Cache and Eviction
Labels:
- neweng

Assigned Teams:

Storage Engines, Storage Engines - Foundations, Storage Engines - Transactions
Sprint:
SE Foundations - 2025-08-01, SE Foundations - 2025-08-15
Story Points:
1

We currently limit the maximum number of eviction threads to 20 (via the eviction.threads_max parameter in api_data.py and via WT_EVICT_MAX_WORKERS). We've had this limit for 14 years. High end configurations now have a lot more CPUs available, and we don't want them to bottleneck on eviction because we can't scale eviction to keep up with CPU counts.

We should increase this limit. 64 seems like a reasonable value.

is related to

WT-14822 Crash in __clayered_copy_constituent_bound due to bound mismatch on layered cursor

Closed

WT-15141 Seg fault in __wt_rec_in_progress

Closed

WT-15097 Add a data handle benchmark for WT

Closed

WT-14960 Review what the address cookie should contain

Closed

WT-15118 Free update chain with prepared update in update restore eviction

Closed

WT-15135 Use unused field for ref_changes instead of extending the ref structure

Closed

related to

WT-14822 Crash in __clayered_copy_constituent_bound due to bound mismatch on layered cursor

Closed

WT-15141 Seg fault in __wt_rec_in_progress

Closed

WT-15097 Add a data handle benchmark for WT

Closed

WT-15118 Free update chain with prepared update in update restore eviction

Closed

WT-15135 Use unused field for ref_changes instead of extending the ref structure

Closed

(1 is related to, 5 related to)

Assignee:: Radoslav Kardum
Reporter:: Keith Smith
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Jul 18 2025 06:41:58 PM UTC
Updated:: Aug 11 2025 04:51:54 AM UTC
Resolved:: Aug 07 2025 08:22:42 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates