Repository navigation
ci: disable CodSpeed process isolation for Rust simulation benchmarks - #10796
Conversation
codspeed-divan-compat 6 runs each benchmark in a new process by default. Simulation measures one iteration without warmup, so each benchmark also pays for a cold allocator and cold caches. This adds about 15 µs to each benchmark and hides small changes in short benchmarks. Signed-off-by: Robert Kruszewski <github@robertk.io> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merging this PR will regress 258 benchmarks3 warnings, 1 note
Warning Please fix the performance issues or acknowledge them on CodSpeed. Performance Changes
Tip Investigate this regression by commenting Comparing Footnotes
|
Summary
codspeed6.0.0 (#10784, #10785) adds process isolation, which is on by default.codspeed-divan-compatnow runs each benchmark in a new copy of the benchmark binary. Simulation mode measures one iteration without warmup, so each benchmark also pays for allocator setup (mimalloc) and for simulated cache misses on memory it touches for the first time. Before, an earlier benchmark in the same process had already paid these costs.The CodSpeed report on #10785 shows a near-constant ~15 µs added to short benchmarks: