[robert3005]

ScalarFnPlugin gains bind_any, which builds the function from options passed as &dyn Any, downcasting them to the function's own ScalarFnVTable::Options type and failing with an error naming that type otherwise.

ScalarFnSessionExt uses it to look a function up in the session's scalar function registry by name and construct the call:

• scalar_fn(name, options) builds the registered function
• call(name, options, args) applies it to args, which are arrays (giving the lazy ScalarFnArray) or expressions (giving the expression), through the new ScalarFnArg trait

[codspeed]

Merging this PR will degrade performance by 2.33%

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 1 benchmark

This benchmark measured no execution time, so its result is not comparable and counts as unchanged. This usually happens when the compiler removes the code under test.

Prevent compiler optimizations

See affected benchmarks

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

⚡ 4 improved benchmarks
❌ 6 regressed benchmarks
✅ 2394 untouched benchmarks
🆕 4 new benchmarks
⏩ 16 skipped benchmarks¹
🗄️ 19 archived benchmarks run²

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	CPU Simulation	bench_compare_primitive[(10000, 32)]	72.9 µs	97.2 µs	-25.05%
❌	CPU Simulation	filter_powerlaw_by_mostly_false[250000]	138.7 µs	158.4 µs	-12.39%
❌	CPU Simulation	test_scan_filter[int]	3.2 ms	3.6 ms	-11.1%
❌	CPU Simulation	filter_random_by_mostly_false[250000]	163.1 µs	183.3 µs	-11.01%
❌	CPU Simulation	filter_powerlaw_by_power_law[250000]	166.1 µs	185.1 µs	-10.25%
❌	CPU Simulation	filter_random_by_power_law[250000]	166 µs	184.9 µs	-10.24%
⚡	CPU Simulation	test_repeated_scan_scalar_at[int]	318.8 µs	239.7 µs	+33.03%
⚡	Walltime	bitpack_blocked_compress_avx2	7.6 µs	6.7 µs	+13.69%
⚡	CPU Simulation	bench_compare_sliced_dict_primitive[(2000, 10000)]	79.9 µs	70.9 µs	+12.75%
⚡	CPU Simulation	prepare_and_compile[1000]	2.4 ms	2.2 ms	+10.74%
🆕	CPU Simulation	pack_bind[100]	N/A	398.1 µs	N/A
🆕	CPU Simulation	pack_bind[200]	N/A	594.5 µs	N/A
🆕	CPU Simulation	pack_bind[350]	N/A	1.1 ms	N/A
🆕	CPU Simulation	pack_bind[500]	N/A	1.5 ms	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/session-call (ceaaf07) with develop (91b38f4)}

Footnotes

1. 16 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. 19 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. ↩