After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit f622139.

Benchmarks with performance regressions

There were 2 possible performance regressions, according to the lookback z-score method.

Benchmarks with regressions:

• Commit Run on ursa-i9-9960x at 2023-10-26 22:16:07Z
  • dataset-serialize (Python) with dataset=nyctaxi_multi_ipc_s3, format=csv, selectivity=10pc
  • dataset-serialize (Python) with dataset=nyctaxi_multi_ipc_s3, format=csv, selectivity=100pc

All benchmark runs analyzed:

• Commit Run on ec2-m5-4xlarge-us-east-2 at 2023-10-26 22:36:17Z
• Commit Run on ursa-i9-9960x at 2023-10-26 22:16:07Z
• Commit Run on ec2-t3-xlarge-us-east-2 at 2023-10-26 22:29:35Z
• Commit Run on arm64-t4g-linux-compute at 2023-10-26 23:11:05Z
• Commit Run on arm64-m6g-linux-compute at 2023-10-26 23:05:22Z

Unstable benchmarks with performance regressions

The following benchmark results indicate a possible performance regression, but are known to sometimes produce false positives when applying the lookback z-score analysis.

• Commit Run on arm64-m6g-linux-compute at 2023-10-26 23:05:22Z
  • BM_ExecSpanIterator (C++) with params=16384, source=cpp-micro, suite=arrow-compute-function-benchmark
  • VarianceKernelInt32 (C++) with params=1048576/100, source=cpp-micro, suite=arrow-acero-aggregate-benchmark
  • BM_ExecSpanIterator (C++) with params=1024, source=cpp-micro, suite=arrow-compute-function-benchmark