Constant canonicalisation uses similar techniques to SparseArray - #9889
robert3005 wants to merge 2 commits into
2 benchmarks regressed
⚠️ 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.
⚡ 4 improved benchmarks
❌ 2 regressed benchmarks
✅ 2196 untouched 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] |
70.4 µs | 94.3 µs | -25.33% |
| ❌ | WallTime | filtered_owned_i64_avx512[OneNullInEight] |
22.8 µs | 26.7 µs | -14.63% |
| ⚡ | Simulation | random_i16[0.95] |
97.7 µs | 80.1 µs | +21.98% |
| ⚡ | WallTime | dict_canonicalize_gt_u8_avx2[16000000] |
7.9 ms | 6.8 ms | +17.06% |
| ⚡ | Simulation | compact_sliced[(1024, 90)] |
1.5 µs | 1.4 µs | +11.92% |
| ⚡ | Simulation | compact_sliced[(2048, 90)] |
1.6 µs | 1.4 µs | +11.42% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing claude/inspiring-maxwell-he0qon (99c8ec3) with develop (c4561ac)
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. ↩