Skip to content

Pack float32 comparison results into bitmap words - #10741

Merged
connortsui20 merged 1 commit into
developfrom
ct/row-fn-cleanup/f32-packing
Oct 26, 2026
Merged

connortsui20 merged 1 commit into
developfrom
ct/row-fn-cleanup/f32-packing

Pack float32 comparison results into bitmap words

bc683bb
Select commit
Loading
Failed to load commit list.
CodSpeed / CodSpeed Performance Analysis succeeded Oct 26, 2026 in 0s

Performance Gate Passed

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

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

⚡ 11 improved benchmarks
✅ 2397 untouched benchmarks
⏩ 12 skipped benchmarks1

Performance Changes

Mode Benchmark BASE HEAD Efficiency
⚡ Walltime compare_f32_avx2 4.4 µs 2.9 µs +51.76%
⚡ Walltime compare_f32_avx512 3.4 µs 2.4 µs +43.97%
⚡ Walltime compare_f32_neon 5.2 µs 4.2 µs +24.21%
⚡ Walltime filter_neon[8] 1,115 ns 917 ns +21.59%
⚡ CPU Simulation test_repeated_scan_scalar_at[int] 280.2 µs 233.7 µs +19.89%
⚡ CPU Simulation test_scan_filter_to_arrow_array[int_float] 4 ms 3.5 ms +16%
⚡ CPU Simulation test_repeated_scan_filter[int_float] 3.9 ms 3.4 ms +13.65%
⚡ Walltime filter_neon[64] 2 µs 1.8 µs +11.94%
⚡ CPU Simulation test_repeated_scan_filter[int] 2.7 ms 2.4 ms +11.19%
⚡ Walltime filter_neon[80] 2.7 µs 2.4 µs +11.02%
⚡ CPU Simulation test_scan_filter_to_arrow_array[int] 2.8 ms 2.5 ms +11.01%

Tip

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


Comparing ct/row-fn-cleanup/f32-packing (bc683bb) with develop (f3cbb32)

Open in CodSpeed

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