feat(array): add probe_scalar to OperationsVTable with a ProbeState shell - #9892
joseph-isaacs wants to merge 1 commit into
Performance Regression: -0.16%
⚠️ 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
❌ 2 regressed benchmarks
✅ 2193 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.7 µs | -24.68% |
| ❌ | Simulation | decompress[u64, (4000, 1024)] |
71.5 µs | 86.9 µs | -17.71% |
| ⚡ | Simulation | random_i16[0.8] |
96.4 µs | 77.8 µs | +23.93% |
| ⚡ | WallTime | words_gather_scalar_avx2[65536] |
9.4 µs | 8.2 µs | +13.82% |
| ⚡ | Simulation | allocate_drop_arrow[0] |
456.9 ns | 402.7 ns | +13.45% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ji/probe-vtable-hook (264e0d4) 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. ↩