[robert3005]

after #10762 we can further split expressions into vortex-expr. We flip dependency order into vortex-array → vortex-expr → vortex-functions.

[codspeed]

Merging this PR will degrade performance by 9.1%

2 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

⚠️ 51 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
❌ 2 regressed benchmarks
✅ 2533 untouched benchmarks
🆕 3 new benchmarks
⏩ 81 skipped benchmarks¹
🗄️ 45 archived benchmarks run²

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	CPU Simulation	take_map[(0.01, 0.05)]	763.6 ns	1,604.4 ns	-52.4%
❌	CPU Simulation	take_map[(0.01, 0.1)]	6.7 µs	7.8 µs	-13.21%
⚡	Walltime	filter_neon[8]	1.4 µs	1.2 µs	+18.89%
⚡	CPU Simulation	stats_compute_is_constant_cached	112.7 µs	99.5 µs	+13.34%
⚡	Walltime	filter_neon[64]	2.2 µs	2 µs	+11.49%
🆕	CPU Simulation	pack_return_dtype[200]	N/A	347.7 µs	N/A
🆕	CPU Simulation	pack_return_dtype[350]	N/A	585.1 µs	N/A
🆕	CPU Simulation	optimize_or_chain[200]	N/A	737.1 µs	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 rk/split-array-07-expr (123df13) with rk/split-array-06-scalar-fns (e33c436)}

Footnotes

1. 81 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. 45 benchmarks were run, but are now archived. If they were deleted in another branch, consider rebasing to remove them from the report. Instead if they were added back, click here to restore them. ↩