[EXPERIMENT] Pass buffer capacity and alignment to the allocator - #9812
[EXPERIMENT] Pass buffer capacity and alignment to the allocator#9812connortsui20 wants to merge 1 commit into
Performance Regression: -7.14%
⚠️ 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.
⚡ 23 improved benchmarks
❌ 43 regressed benchmarks
✅ 2121 untouched benchmarks
⏩ 218 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | allocate_drop_vortex[64] |
3 µs | 7.6 µs | -61.2% |
| ❌ | Simulation | bitwise_and_vortex_buffer[128] |
4 µs | 8.7 µs | -54% |
| ❌ | Simulation | bitwise_or_vortex_buffer[128] |
4.1 µs | 8.8 µs | -53.32% |
| ❌ | Simulation | allocate_drop_vortex_custom[64] |
3.6 µs | 7.5 µs | -51.43% |
| ❌ | Simulation | bitwise_not_vortex_buffer[128] |
4.7 µs | 9.5 µs | -50.8% |
| ❌ | Simulation | allocate_freeze_drop_arrow[64] |
3.6 µs | 7.1 µs | -49.73% |
| ❌ | Simulation | bitwise_and_vortex_buffer[1024] |
4.3 µs | 8.4 µs | -49.15% |
| ❌ | Simulation | bitwise_and_vortex_buffer[2048] |
4.7 µs | 9.1 µs | -48.4% |
| ❌ | Simulation | allocate_freeze_drop_vortex_custom[64] |
4.3 µs | 8.3 µs | -48.03% |
| ❌ | Simulation | collect_bool_u32_gt[1024] |
10.7 µs | 14.2 µs | -24.95% |
| ❌ | Simulation | allocate_freeze_drop_vortex_custom[256] |
6.2 µs | 8.2 µs | -24.04% |
| ❌ | Simulation | allocate_freeze_drop_vortex[16384] |
6 µs | 7.7 µs | -21.45% |
| ❌ | Simulation | allocate_freeze_drop_vortex[65536] |
6 µs | 7.7 µs | -21.35% |
| ❌ | Simulation | new_raw_prim_test_between[i32, 2048] |
62 µs | 77.9 µs | -20.44% |
| ❌ | Simulation | allocate_drop_arrow[0] |
456.9 ns | 568 ns | -19.56% |
| ❌ | Simulation | allocate_freeze_drop_vortex[64] |
3.5 µs | 4.3 µs | -18.85% |
| ❌ | Simulation | random_i16[0.8] |
74.6 µs | 91.4 µs | -18.35% |
| ❌ | Simulation | allocate_drop_vortex[65536] |
6.4 µs | 7.9 µs | -18.02% |
| ❌ | Simulation | preverify_advancing_ptr_unchecked[1000] |
11.5 µs | 13.9 µs | -17.71% |
| ❌ | Simulation | allocate_drop_vortex[16384] |
6.4 µs | 7.8 µs | -16.98% |
| ... | ... | ... | ... | ... | ... |
ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ct/buffer-allocation-boundary (22ef33a) with develop (402fd1d)
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. ↩