fix(buffer): avoid shrinking allocations through grow - #10030
1 benchmark 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.
⚠️ 3 benchmarks measured no execution time
Nothing ran under measurement, usually because the compiler removed the code under test. These results are not comparable, so they count as unchanged.
⚠️ 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
❌ 1 regressed benchmark
✅ 2171 untouched benchmarks
⏩ 385 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | WallTime | filtered_sink_i64_avx512[OneNullInEight] |
22.4 µs | 26.3 µs | -15.13% |
| ⚡ | WallTime | filtered_sink_i64_avx2[OneNullInEight] |
26.2 µs | 21.9 µs | +19.52% |
| ⚡ | WallTime | decode_avx512[8192, (Inline, OneNullInEight)] |
93.8 µs | 81.2 µs | +15.53% |
| ⚡ | WallTime | dict_canonicalize_gt_u8_neon[1000000] |
549.8 µs | 488.4 µs | +12.56% |
| ⚡ | Simulation | set_indices_vortex_buffer[128] |
2.1 µs | 1.8 µs | +12.01% |
| Simulation | fixed_16_advancing_ptr_safe[100] |
< 1 ns | < 1 ns | N/A | |
| Simulation | preverify_advancing_ptr_unchecked[1000] |
< 1 ns | < 1 ns | N/A | |
| Simulation | preverify_advancing_ptr_unchecked[10000] |
< 1 ns | < 1 ns | N/A |
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-grow-layout (b0aa3bc) with develop (2d9414a)
Footnotes
-
385 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. ↩