Skip to content

Support wide decimals in DecimalByteParts and guarantee compat with editions - #9759

Draft
mhk197 wants to merge 28 commits into
developfrom
mk/dbp-v2
Draft

Support wide decimals in DecimalByteParts and guarantee compat with editions#9759
mhk197 wants to merge 28 commits into
developfrom
mk/dbp-v2

Revert "Stage vortex.decimal_byte_parts_v2 in preview2026.09.0"

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

3 benchmarks 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

⚡ 3 improved benchmarks
❌ 3 regressed benchmarks
✅ 2235 untouched benchmarks
🆕 2 new benchmarks
⏩ 164 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_i16[0.8] 75.1 µs 93.8 µs -19.88%
Simulation allocate_drop_bytes[0] 466 ns 520.2 ns -10.41%
WallTime mul_i32_nonnull_avx512 7 µs 7.8 µs -10.3%
Simulation random_i8[0.5] 91.3 µs 67.9 µs +34.43%
WallTime arrow_checked_add_u32_avx512[16384] 21.4 µs 17.6 µs +21.3%
WallTime words_gather_scalar_avx2[65536] 9.4 µs 8.3 µs +13.27%
🆕 Simulation canonicalize_byte_parts[1] N/A 2 ms N/A
🆕 Simulation canonicalize_byte_parts[3] N/A 6 ms 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 mk/dbp-v2 (79a8058) with develop (0d9d5b8)

Open in CodSpeed

Footnotes

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