bench(pco): per-element scalar reads across and within chunks - #9895
joseph-isaacs wants to merge 1 commit into
Performance Regression: -8.55%
⚠️ 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.
⚠️ Different runtime environments detected
Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.
⚡ 1 improved benchmark
❌ 2 regressed benchmarks
✅ 2195 untouched benchmarks
🆕 2 new benchmarks
⏩ 218 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | random_i8[0.5] |
71.3 µs | 94.8 µs | -24.77% |
| ❌ | Simulation | decompress[u64, (4000, 1024)] |
71.5 µs | 86.8 µs | -17.63% |
| ⚡ | Simulation | random_i16[0.8] |
96.4 µs | 78.1 µs | +23.41% |
| 🆕 | Simulation | scalar_at_one_per_chunk |
N/A | 6.5 ms | N/A |
| 🆕 | Simulation | scalar_at_within_one_chunk |
N/A | 12.6 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 ji/pco-scalar-at-bench (cd4231c) with develop (b5f43ba)
Footnotes
-
218 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. ↩