[connortsui20]

Tracking Issue: #10701

Stacked on #11003. #11005 builds on it. No release gate.

Summary

Decimal widening preserves order, equality and validity, so ordered aggregates can use the child instead of copying it first. Sum also needs the logical result precision: using the child's sum dtype could overflow a result that should fit.

Changes

Ordered aggregates widen their child partials, and MinMax reuses exact cached child extrema before scanning. Decimal Sum runs in the logical sum dtype only when the legacy Stat::Sum path combines independent batch totals. SumV2 and Sum without skip_nans keep the fallback because their running sum can cancel a batch total that would overflow on its own. Tests compare running partials against fresh canonical batches so cached statistics cannot hide kernel work.

Historical local benchmark results

These retained measurements predate this style pass and rebase. They do not measure the current head.

cargo bench -p vortex-array --bench widen_decimal, Apple M4, medians. The numbers were measured at the top of this stack before the split, so they cover the whole stack, not this layer alone. The baseline is the canonical input, and the candidate is the same values as a Widen (child precision 5 under precision 10, 9 under 18, and 18 under 38). CodSpeed on this PR measures the layer itself.

bench	p10 canonical	p10 Widen	p18 canonical	p18 Widen	p38 canonical	p38 Widen
min_max	14.93 µs	15.12 µs	14.62 µs	15.12 µs	21.58 µs	14.95 µs

sum medians are within 8% of the canonical input at every precision.

API Changes

None.

[codspeed]

Merging this PR will regress 3 benchmarks

1 warning

⚠️ 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

⚡ 3 improved benchmarks
❌ 3 regressed benchmarks
✅ 1876 untouched benchmarks
⏩ 469 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	CPU Simulation	encode_primitives[f32, (2000, 2)]	176.9 µs	204.5 µs	-13.5%
❌	CPU Simulation	take_filter_primitive_small_uncached_random_mask_random_indices[4096, 10]	21.9 µs	24.4 µs	-10.45%
❌	Walltime	lt_i64_nullable_avx512	7.4 µs	8.2 µs	-10.22%
⚡	CPU Simulation	bench_compare_varbin[(50000, 2)]	162.4 µs	132.3 µs	+22.71%
⚡	CPU Simulation	bench_compare_sliced_dict_varbinview[(1000, 10000)]	90.3 µs	78.7 µs	+14.68%
⚡	CPU Simulation	bench_compare_sliced_dict_varbinview[(9999, 10000)]	233.6 µs	205.9 µs	+13.46%

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-widen-aggregates (65ea070) with develop (1ec5a1b)}

Footnotes

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