Remove ArrayAccessor#8603
Performance Regression: -8.05%
⚠️ 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.
⚡ 5 improved benchmarks
❌ 10 regressed benchmarks
✅ 1574 untouched benchmarks
⏩ 4 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | take_map[(0.1, 1.0)] |
1.6 ms | 2.4 ms | -30.95% |
| ❌ | Simulation | take_map[(0.1, 0.5)] |
987.2 µs | 1,380.1 µs | -28.47% |
| ❌ | Simulation | take_map[(0.01, 1.0)] |
1.2 ms | 1.6 ms | -26.84% |
| ❌ | Simulation | take_map[(0.01, 0.1)] |
161.8 µs | 200 µs | -19.09% |
| ❌ | Simulation | chunked_varbinview_into_canonical[(1000, 10)] |
169 µs | 205.5 µs | -17.79% |
| ❌ | Simulation | take_map[(0.01, 0.05)] |
106.2 µs | 124.5 µs | -14.71% |
| ❌ | Simulation | slice_empty_vortex |
339.4 ns | 397.8 ns | -14.66% |
| ❌ | Simulation | take_map[(0.01, 0.5)] |
603.1 µs | 703.3 µs | -14.25% |
| ❌ | Simulation | take_map[(0.1, 0.1)] |
455.3 µs | 529.1 µs | -13.95% |
| ❌ | Simulation | take_map[(0.005, 1.0)] |
1.1 ms | 1.3 ms | -11.66% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[128] |
244.4 ns | 186.1 ns | +31.34% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[1024] |
304.7 ns | 246.4 ns | +23.68% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[2048] |
398.6 ns | 340.3 ns | +17.14% |
| ⚡ | Simulation | chunked_varbinview_canonical_into[(100, 100)] |
259.7 µs | 224.5 µs | +15.7% |
| ⚡ | Simulation | chunked_varbinview_into_canonical[(100, 100)] |
306.5 µs | 271.1 µs | +13.05% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing rk/noarrayaccessor (ec21168) with develop (f172d58)
Footnotes
-
4 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. ↩