Add benchmark budget enforcement with CI reporting - #9150
Performance Regression: -14.22%
⚠️ 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.
❌ 1 regressed benchmark
✅ 1884 untouched benchmarks
🆕 1 new benchmark
⏩ 12 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | WallTime | cuda/bitpacked_u8/unpack/3bw[100M] |
299.9 µs | 349.6 µs | -14.22% |
| 🆕 | Simulation | over_budget_prefix_count |
N/A | 16.2 ms | N/A |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing claude/codspeed-benchmark-ci-check-d50h60 (40c3940) with develop (aa7cd40)
Footnotes
-
12 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. ↩