[connortsui20]

Summary

• Tracking Issue: Tracking Issue: Fix Canonical Decimal #10701

Adds benchmarks for the decimal paths that #10701 changes, so CodSpeed has a base before those changes land. They cover compute on DecimalByteParts arrays whose most significant part is narrower than the canonical width (decode, compare, filter, sum and min-max), a compressed DecimalByteParts tree in the decompress throughput bench, casts that grow the canonical width, and decimal export to Arrow and DuckDB.

Changes

The DecimalByteParts compute, decompress and cast benches run in CodSpeed. The Arrow and DuckDB export benches run locally only, because those crates have no CodSpeed shard, and the decimal compress bench stays inside the existing cfg(not(codspeed)) module. The compress bench enables the default core edition, so the decimal scheme uses its v1 variant as in a default write. vortex-duckdb gains a #[doc(hidden)] _benchmarking module that re-exports ArrayExporter and ConversionCache for its bench, and the fields of ConversionCache become pub(crate) so that the module exposes only the type. No library behavior changes. Every input is a canonical decimal or a DecimalByteParts array, so the benches stay valid once every decimal array must have the canonical width.

🤖 Generated with Claude Code

[codspeed]

Merging this PR will regress 4 benchmarks

3 warnings, 1 note

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ Unable to measure the execution of 2 benchmarks

These benchmarks measured no execution time, so their results are not comparable and count as unchanged. This usually happens when the compiler removes the code under test.

Prevent compiler optimizations

See affected benchmarks

⚠️ 23 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

ℹ️ 40 benchmarks have no flamegraph

The flamegraph wasn't generated: the symbols of the profiling trace could not be resolved, because no information about the language frames was collected.

See affected benchmarks

⚡ 3 improved benchmarks
❌ 4 regressed benchmarks
✅ 2401 untouched benchmarks
🆕 31 new benchmarks
⏩ 12 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	CPU Simulation	test_scan_filter_to_arrow_array[int_float]	3.5 ms	4.1 ms	-14.77%
❌	CPU Simulation	test_repeated_scan_filter[int_float]	3.4 ms	3.9 ms	-12.15%
❌	CPU Simulation	test_repeated_scan_filter[int]	2.4 ms	2.7 ms	-10.33%
❌	CPU Simulation	test_scan_filter_to_arrow_array[int]	2.5 ms	2.8 ms	-10.17%
⚡	CPU Simulation	bench_compare_primitive[(10000, 32)]	97 µs	72.9 µs	+33.16%
⚡	CPU Simulation	chunked_dict_primitive_canonical_into[f64, (1000, 1000, 10)]	191.7 µs	151.7 µs	+26.38%
⚡	Walltime	starts_with_avx2[8, VarBin]	46.9 µs	41 µs	+14.33%
🆕	CPU Simulation	compare_constant_out_of_range[gap_msp_i16_p10]	N/A	46 µs	N/A
🆕	CPU Simulation	compare_constant_out_of_range[msp_i32_p18]	N/A	68 µs	N/A
🆕	CPU Simulation	compare_constant_out_of_range[msp_i64_p38]	N/A	46 µs	N/A
🆕	CPU Simulation	compare_constant[gap_msp_i16_p10]	N/A	90.5 µs	N/A
🆕	CPU Simulation	compare_constant[msp_i32_p18_nullable]	N/A	105.6 µs	N/A
🆕	CPU Simulation	compare_constant[msp_i32_p18]	N/A	125 µs	N/A
🆕	CPU Simulation	compare_constant[msp_i64_p18_canonical]	N/A	131.8 µs	N/A
🆕	CPU Simulation	compare_constant[msp_i64_p38]	N/A	132.2 µs	N/A
🆕	CPU Simulation	decode[gap_msp_i16_p10]	N/A	22.4 µs	N/A
🆕	CPU Simulation	decode[msp_i32_p18_nullable]	N/A	23.7 µs	N/A
🆕	CPU Simulation	decode[msp_i32_p18]	N/A	22.5 µs	N/A
🆕	CPU Simulation	decode[msp_i64_p18_canonical]	N/A	22.5 µs	N/A
🆕	CPU Simulation	decode[msp_i64_p38]	N/A	22.5 µs	N/A
...	...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

Tip

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

---

_{Comparing ct/decimal-benchmarks (5778fab) with develop (3974ee0)}

Footnotes

1. 12 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. ↩