-
Type:
Build Failure
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Not Applicable
-
Storage Engines - Persistence
-
637.219
-
StorEng - Defined Pipeline
-
None
A recent change affecting the wiredtiger evergreen project has potentially caused performance changes to one or more automated performance tests.
- Commit info - 6127089, 2026-09-04
- Failing Evergreen Task
This Perf BF may contain both regressions and improvements with the emphasis being drawn to regressions. On the Perf BF page, you may filter out regressions by selecting the corresponding Change Type (far left) column in the table.
- All performance metrics, tasks and tests that have been altered as a result of this change can be found in the Full list of change points for this BF

When closing this ticket, please populate the 'Fix revision' field if appropriate.
- is caused by
-
WT-18187 Optimize disaggregated publish check with a per-btree create_schema_epoch field
-
- Closed
-
- is fixed by
-
WT-18587 Merge tiered storage removal into develop
-
- Closed
-
- is related to
-
WT-18532 Follower timestamped reader can bind a superseded checkpoint after its data was pruned from the ingest table - stale read
-
- Closed
-
-
WT-15917 Remove the redundant code that do more scrub eviction for disagg
-
- Closed
-
-
WT-18336 __clayered_ignore_missing_stable's step-down-timestamp check can hide a genuinely missing stable constituent
-
- Closed
-
-
WT-18534 __wt_btree_is_outdated_disagg uses || instead of && between DISAGGREGATED and READONLY checks
-
- Closed
-
-
WT-18550 Checkpoint cleanup dirties a fully deleted disaggregated internal page for a no-progress rewrite before its truncate is globally visible
-
- Closed
-
-
WT-18665 Bucket unit-test-zstd for faster merge queue
-
- Closed
-
-
WT-18658 Walk checkpoint's connection-wide handle list backwards instead of sweep's
-
- Closed
-