Install libc debug symbols for codspeed benchmarks#8384
Performance Regression: -17.99%
⚠️ 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.
❌ 6 regressed benchmarks
✅ 1520 untouched benchmarks
⏩ 10 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.4 µs | 35.4 µs | -42.42% |
| ❌ | Simulation | chunked_varbinview_into_canonical[(1000, 10)] |
176.8 µs | 212.9 µs | -16.98% |
| ❌ | Simulation | chunked_varbinview_canonical_into[(100, 100)] |
272.7 µs | 307.9 µs | -11.41% |
| ❌ | Simulation | encode_varbin[(1000, 4)] |
142.9 µs | 159.9 µs | -10.61% |
| ❌ | Simulation | encode_varbin[(1000, 8)] |
143.6 µs | 160.6 µs | -10.61% |
| ❌ | Simulation | encode_varbin[(1000, 32)] |
148.5 µs | 165.2 µs | -10.09% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing adamg/codspeed-libc-dbg (b4882ac) with develop (c6a0b7b)
Footnotes
-
10 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. ↩