Skip to content

Support wide decimals in DecimalBytePartsArray and kernels - #9809

Open
mhk197 wants to merge 2 commits into
mk/dbp-partsfrom
mk/dbp-array
Open

Support wide decimals in DecimalBytePartsArray and kernels#9809
mhk197 wants to merge 2 commits into
mk/dbp-partsfrom
mk/dbp-array

Simplify decimal byte-parts array helpers

9a179ed
Select commit
Loading
Failed to load commit list.
CodSpeed HQ / CodSpeed Performance Analysis failed Sep 9, 2026 in 0s

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.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 7 improved benchmarks
❌ 1 regressed benchmark
✅ 2254 untouched benchmarks
⏩ 194 skipped benchmarks1
🗄️ 1 archived benchmark run2

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
Simulation random_i8[0.8] 69.5 µs 99 µs -29.76%
WallTime words_gather_dispatch_neon[1024] 47 ns 30 ns +56.67%
Simulation random_i8[0.5] 91.1 µs 67.1 µs +35.71%
WallTime arrow_checked_add_u32_avx2[16384] 21.3 µs 17.6 µs +21.03%
WallTime words_gather_scalar_avx2[65536] 9.4 µs 8.2 µs +13.63%
Simulation allocate_drop_arrow[0] 456.9 ns 402.7 ns +13.45%
WallTime add_shapes_neon[(128, PerRowPerRow)] 2.1 µs 1.9 µs +13.01%
Simulation allocate_drop_bytes[0] 575.7 ns 521.6 ns +10.39%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing mk/dbp-array (9a179ed) with mk/dbp-parts (1f2143a)

Open in CodSpeed

Footnotes

  1. 194 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.

  2. 1 benchmark was run, but is now archived. If it was deleted in another branch, consider rebasing to remove it from the report. Instead if it was added back, click here to restore it.