perf(fsst): gather sparse takes from small arrays with large payloads - #10509

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. This result is not comparable, so it counts as unchanged.

Preventing compiler optimizations

• 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

• density_sweep_dense_runs[0.001]
• take_indices[(10000, 4096)]
• test_scan_filter[int_str_float]
• test_scan_filter[int_float]
• random_i128[0.01]
• test_scan_filter[int_str]
• decompress[u16, (4000, 256)]
• test_scan[int_str_float]
• test_scan[int_str]
• ilike_contains
• …and 6 more

The flamegraph could not be generated because we failed to resolve the symbols in the profiling trace. This happens when we fail to harvest information about language frames.

• test_scan_filter_to_arrow_array[int_float]
• test_repeated_scan_filter[int_float]
• test_repeated_scan_filter[int]
• test_scan_filter_to_arrow_array[int]
• test_scan_filter[int]
• test_repeated_scan_to_arrow_array[int]
• test_repeated_scan_scalar_at[int_float]
• test_scan_scalar_at[int_float]
• test_scan_filter[int_str_float]
• test_scan_filter[int_float]
• …and 30 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