Reduce variance in sort benchmarks by reusing temp file #8939
+28
−21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug existed since Sept 2024 but variance was below CodSpeed's threshold (~1-3%). On Oct 11, CI changed to run 19 benchmarks in parallel (f19d7ec, 6df73f0) instead of sequentially. This amplified
/tmp
contention, pushing variance to 2.64%—above detection threshold. The parallel execution exposed what was always there.Solution
Move
NamedTempFile::new()
outside loop, matchingsort_bench.rs
pattern:Eliminates filesystem noise while preserving correct semantics (sort overwrites file each iteration, no caching)
Notes
Affected PRs: #8935, #8936, #8927, #8926, #8930, #8932.