feat(array): scalar probes with one-off and repeated probe types - #9890
joseph-isaacs wants to merge 2 commits into
3 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.
⚡ 3 improved benchmarks
❌ 3 regressed benchmarks
✅ 2192 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] |
71.3 µs | 94 µs | -24.1% |
| ❌ | Simulation | new_raw_prim_test_between[i32, 2048] |
64.1 µs | 77.1 µs | -16.84% |
| ❌ | WallTime | dict_canonicalize_gt_u8_neon[1000000] |
487.8 µs | 569.4 µs | -14.32% |
| ⚡ | Simulation | execute_scalar_struct_wide |
503 µs | 394.1 µs | +27.62% |
| ⚡ | Simulation | random_i16[0.8] |
96.4 µs | 77.5 µs | +24.5% |
| ⚡ | Simulation | execute_scalar_struct_simple |
106.5 µs | 90.3 µs | +17.92% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ji/array-probe-enum-state (8a4beb1) 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. ↩