Optimise bitpacked filtering and take for valid runs - #10281

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.

Nothing ran under measurement, usually because the compiler removed the code under test. These results are not comparable, so they count as unchanged.

Preventing compiler optimizations

• bench_compare_primitive[(10000, 2)]
• bench_compare_sliced_dict_primitive[(3333, 10000)]

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

• random_i128[0.01]
• decompress[u16, (4000, 256)]
• fsl_i32[2, 0.5]
• test_scan_to_arrow_array[int]
• take_indices[(10000, 4096)]
• test_scan_scalar_at[int]
• test_scan_filter[int_str_float]
• test_scan_filter_to_arrow_array[int_str_float]
• test_scan_filter[int_float]
• from_vec_drop_vortex[65536]
• …and 9 more

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