[robert3005]

The generic constructors (ConstantArray::new<S>, PrimitiveArray::{new, try_new, new_unchecked, empty}<T>, DecimalArray::{try_new, new_unchecked}<T>, and the impl IntoIterator constructors of StructArray and ChunkedArray) called the generic Array::from_parts_unchecked and Array::try_from_parts directly. Each crate that called them monomorphized its own copy of those functions and of the full DynArrayData vtable for the encoding.

The generic constructors now call a private, non-generic builder. vortex-array compiles each vtable once, and other crates call it. ScalarFn had the same problem because new_from_validated_slots was #[inline], and it is not inlined now. The cost is one function call when an array is constructed.

vortex-ffi release cdylib (macOS arm64)	before	after
__text	37,223,740 B	36,613,308 B (-610 KB)
Copies of the vtable: Constant / Primitive / Struct / Chunked / Decimal / ScalarFn	22 / 17 / 7 / 5 / 5 / 4	1 / 1 / 1 / 1 / 1 / 1

[codspeed]

Merging this PR will degrade performance by 5.18%

4 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

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

⚠️ Base and head ran on different runner types

Some benchmarks with significant performance changes were compared across different runner types, so the changes might not come from the code. Run base and head on the same runner type, or use CodSpeed Macro Runners for more stable results.

Learn more about Macro Runners

Open the report in CodSpeed to investigate

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

⚡ 7 improved benchmarks
❌ 4 regressed benchmarks
✅ 2428 untouched benchmarks
⏩ 12 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	CPU Simulation	bench_compare_sliced_dict_primitive[(3333, 10000)]	32.9 µs	72.8 µs	-54.72%
❌	Walltime	mul_u64_nonnull_neon	20.6 µs	39.1 µs	-47.43%
❌	CPU Simulation	filter_powerlaw_by_random[250000]	131.3 µs	175.3 µs	-25.11%
❌	CPU Simulation	new_bp_prim_test_between[i16, 2048]	53.6 µs	68.1 µs	-21.33%
⚡	CPU Simulation	new_raw_prim_test_between[i32, 2048]	76.2 µs	53.5 µs	+42.48%
⚡	CPU Simulation	chunked_dict_primitive_canonical_into[f64, (1000, 1000, 10)]	203.3 µs	147.2 µs	+38.05%
⚡	CPU Simulation	compare[1]	124.3 µs	102.7 µs	+21.03%
⚡	CPU Simulation	missing_stats[16]	83.4 µs	69.4 µs	+20.14%
⚡	CPU Simulation	decompress[u16, (4000, 256)]	62.5 µs	55.2 µs	+13.29%
⚡	Walltime	add_constant_shapes_neon[(32768, ConstantPerRow)]	15.8 µs	14.3 µs	+10.98%
⚡	Walltime	add_constant_shapes_neon[(32768, PerRowConstant)]	15.8 µs	14.3 µs	+10.45%

Tip

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

---

_{Comparing rk/size-nongeneric-array-ctors (b68f68b) with develop (76d8371)}

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