feat: add bitpacked chunk offset child - #9940
Performance Regression: -22.08%
⚠️ 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 regressed benchmarks
✅ 216 untouched benchmarks
⏩ 2342 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ❌ | arrow_checked_add_u32_neon[16384] |
12.3 µs | 20.4 µs | -39.83% |
| ❌ | dbp_split_kernel_mixed_null_neon[(I256, 1024)] |
1.9 µs | 2.2 µs | -12.21% |
| ❌ | mul_u32_nonnull_avx512 |
5.6 µs | 6.3 µs | -10.44% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing mk/bitpacked-stack-04-offset-child (ecd1bd3) with mk/bitpacked-stack-03-width-child (6dc1734)
Footnotes
-
2342 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. ↩