[joseph-isaacs]

• New AggregateFnSession::register_storage_ordered(ext) pushes the comparison-based aggregates is_sorted and min_max down into ext's storage, registering ExtensionStoragePushdown<IsSorted, E> and ExtensionStoragePushdown<MinMax, E>.
• The default aggregate session calls it for Date, Time and Timestamp, whose storage is an integer.
• vortex_uuid::initialize calls it for Uuid. UUIDs are stored as 16 big-endian bytes, so byte order is UUID order.
• is_sorted and min_max now order a FixedSizeList of non-nullable u8 (UUID storage) lexicographically by byte. A shared fns/fixed_size_bytes.rs decodes the elements once and slices each value. Other fixed-size lists stay unsupported.

[codspeed]

Merging this PR will improve performance by 19.44%

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

⚠️ 1 benchmark measured no execution time

Nothing ran under measurement, usually because the compiler removed the code under test. This result is not comparable, so it counts as unchanged.

Preventing compiler optimizations

• bench_compare_primitive[(10000, 2)]

⚠️ 32 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• decode_primitives[i64, (1000, 8)]
• random_i128[0.01]
• test_scan_scalar_at[int]
• density_sweep_dense_runs[0.001]
• test_scan_read_all_to_arrow_array[int_float]
• test_repeated_scan_scalar_at[int]
• test_repeated_scan_to_arrow_array[int]
• test_scan_filter[int_str_float]
• test_repeated_scan_to_arrow_array[int_float]
• test_scan_filter[int_float]
• …and 22 more

ℹ️ 40 benchmarks have no flame graph

The flamegraph could not be generated because we failed to resolve the symbols in the profiling trace. This happens when we fail to harvest information about language frames.

• test_scan_filter[int]
• test_scan_scalar_at[int]
• test_scan_read_all_to_arrow_array[int_float]
• test_repeated_scan_scalar_at[int]
• test_repeated_scan_to_arrow_array[int]
• test_scan_filter[int_str_float]
• test_repeated_scan_to_arrow_array[int_float]
• test_scan_filter[int_float]
• test_repeated_scan_filter[int]
• test_scan_filter[int_str]
• …and 30 more

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

⚡ 8 improved benchmarks
✅ 2400 untouched benchmarks
⏩ 12 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡ ⚠️	Simulation	decode_primitives[i64, (1000, 8)]	37.5 µs	23.8 µs	+57.32%
⚡	Simulation	chunked_opt_bool_canonical_into[(1000, 10)]	65.4 µs	55.1 µs	+18.65%
⚡	WallTime	threshold_neon[80]	4.2 µs	3.6 µs	+18.52%
⚡	WallTime	filter_neon[64]	2 µs	1.8 µs	+16.33%
⚡ ⚠️	Simulation	random_i128[0.01]	6.1 µs	5.3 µs	+15.18%
⚡	Simulation	random_i8[0.01]	117 µs	103.3 µs	+13.35%
⚡	WallTime	threshold_neon[8]	1.5 µs	1.4 µs	+11.73%
⚡	WallTime	words_gather_dispatch_neon[65536]	2 µs	1.8 µs	+10.38%

Tip

Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing ji/extension-order-aggregates (b055982) with develop (cb39bb9)}

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

[joseph-isaacs]

CodSpeed Performance Analysis is red here, and I don't think this PR causes it.

The only runtime change is six more entries in the default aggregate session's registry, plus deleting an unreachable IsSorted branch. The flagged benchmarks are random_i128 filtering, run-end decompress, ilike_contains, take_varbin, chunked dict canonicalization and Python scans. None of them binds or accumulates an aggregate, and none of them looks anything up in that registry.

The regression count also moves without a code change. a1d0943 flagged 29 benchmarks, and b09c7ed, which only changes test code, flags 18. Most of the benchmarks also appear on #10566 and other PRs. CodSpeed's report itself warns about walltime runs on hosted runners and about benchmarks that spend significant time in system calls.

No fix is needed in this PR. The regressions can be acknowledged on CodSpeed.

---

Generated by Claude Code

[connortsui20]

Is there a way to have more specialized logic for certain UUID extension types? for example, with UUIDv7 we want to only compare the timestamp parts rather than the whole ID lexicographically