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

Benchmarks with performance regressions

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

Benchmarks with regressions:

• Commit Run on ursa-i9-9960x at 2023-08-18 08:41:22Z
  • dataset-selectivity (Python) with dataset=nyctaxi_multi_ipc_s3, selectivity=10%
  • dataset-selectivity (Python) with dataset=nyctaxi_multi_ipc_s3, selectivity=1%
  • dataset-selectivity (Python) with dataset=nyctaxi_multi_parquet_s3, selectivity=100%
  • dataset-selectivity (Python) with dataset=nyctaxi_multi_ipc_s3, selectivity=100%

All benchmark runs analyzed:

• Commit Run on ursa-i9-9960x at 2023-08-18 08:41:22Z
• Commit Run on ec2-m5-4xlarge-us-east-2 at 2023-08-18 08:57:21Z
• Commit Run on arm64-m6g-linux-compute at 2023-08-18 09:47:33Z
• Commit Run on ec2-t3-xlarge-us-east-2 at 2023-08-18 08:53:33Z
• Commit Run on arm64-t4g-linux-compute at 2023-08-18 09:53:04Z
• Commit Run on ursa-thinkcentre-m75q at 2023-08-19 01:28:23Z

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 ursa-thinkcentre-m75q at 2023-08-19 01:28:23Z
  • TouchArea (C++) with params=size:4096/real_time, source=cpp-micro, suite=arrow-memory-pool-benchmark
  • FilterInt64FilterNoNulls (C++) with params=524288/5, source=cpp-micro, suite=arrow-compute-vector-selection-benchmark