Skip to content

Add ArrayPlugin to enable serde for new DecimalBytePartsArray format - #9810

Open
mhk197 wants to merge 4 commits into
mk/dbp-arrayfrom
mk/dbp-serde
Open

Add ArrayPlugin to enable serde for new DecimalBytePartsArray format#9810
mhk197 wants to merge 4 commits into
mk/dbp-arrayfrom
mk/dbp-serde

fix comment

72f2396
Select commit
Loading
Failed to load commit list.
CodSpeed HQ / CodSpeed Performance Analysis failed Sep 10, 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

⚡ 4 improved benchmarks
❌ 1 regressed benchmark
✅ 2200 untouched benchmarks
⏩ 224 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
WallTime arrow_checked_add_u32_avx2[16384] 17.7 µs 21.3 µs -17.06%
Simulation allocate_drop_arrow[0] 456.9 ns 402.7 ns +13.45%
WallTime filtered_owned_i64_avx512[OneNullInEight] 26.2 µs 23.2 µs +12.92%
WallTime mul_u32_nonnull_avx512 6.3 µs 5.6 µs +11.29%
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-serde (72f2396) with mk/dbp-array (7283d4f)2

Open in CodSpeed

Footnotes

  1. 224 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. No successful run was found on mk/dbp-array (a20094e) during the generation of this report, so 0b5c37d was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.