-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Performance
-
Storage Engines - Foundations
-
None
-
None
A recent change affecting the sys-perf evergreen project has caused 1 regression and 0 improvements across 1 test in 1 task for 1 measurement. Overall, no high value workloads were affected.
Commit info - 07d6698, 2026-04-17
All performance metrics, tasks and tests that have been affected as a result of this change can be found in this:
- Full list of change points for this BF (view the summary tab for aggregate data on this BF)
Some example change points that occurred are:
Note: Metadata and source location for affected workloads can be found by hovering over the data points in the trends charts
Please reach out to #ask-devprod-performance or #perf-build-baroning if you need help running workloads.
Some helpful links:
- Performance workloads documentation
- Analyzing Performance of Code Changes
- Guide to Metrics Reported by Performance Tests
- Guide for Investigating a Performance Change
- Guide for Validating a Performance Change
- Guide for Investigating Binary Layout Issues
When closing this ticket, please populate the 'Fix revision' field if appropriate.
- is related to
-
WT-16728 Prioritize page-split realization to avoid expensive re-reconciliation behaviour
-
- Closed
-