Migrate to new stats falsification rules#8345
Performance Regression: -11.36%
⚠️ Unknown Walltime execution environment detected
Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.
For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.
⚡ 2 improved benchmarks
❌ 4 regressed benchmarks
✅ 1575 untouched benchmarks
⏩ 11 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | chunked_bool_canonical_into[(1000, 10)] |
20.3 µs | 35.8 µs | -43.31% |
| ❌ | Simulation | chunked_varbinview_into_canonical[(1000, 10)] |
177.7 µs | 215.4 µs | -17.52% |
| ❌ | Simulation | decompress_rd[f64, (100000, 0.1)] |
890.7 µs | 1,024.6 µs | -13.07% |
| ❌ | Simulation | decompress_rd[f64, (100000, 0.01)] |
890.7 µs | 1,024.6 µs | -13.07% |
| ⚡ | WallTime | cuda/bitpacked_u8/unpack/3bw[100M] |
352 µs | 298.7 µs | +17.84% |
| ⚡ | Simulation | varbinview_large |
131 µs | 112.4 µs | +16.53% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ngates/public-stats-rewrite-rules (d81033e) with develop (85aad72)
Footnotes
-
11 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩