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

Benchmarks with performance regressions

There was 1 possible performance regression, according to the lookback z-score method.

Benchmarks with regressions:

• Commit Run on test-mac-arm at 2024-10-02 10:22:41Z
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-18, scale_factor=1

All benchmark runs analyzed:

• Commit Run on amd64-c6a-4xlarge-linux at 2024-10-02 09:59:28Z
• Commit Run on arm64-t4g-2xlarge-linux at 2024-10-02 10:17:11Z
• Commit Run on test-mac-arm at 2024-10-02 10:22:41Z
• Commit Run on amd64-m5-4xlarge-linux at 2024-10-02 10:11:25Z

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 test-mac-arm at 2024-10-02 10:22:41Z
  • UniqueString100bytes (C++) with params=0, source=cpp-micro, suite=arrow-compute-vector-hash-benchmark
  • UniqueString100bytes (C++) with params=2, source=cpp-micro, suite=arrow-compute-vector-hash-benchmark
  • BenchmarkTemporalBinary (C++) with params=<MonthsBetween, non_zoned>/4194304/100, source=cpp-micro, suite=arrow-compute-scalar-temporal-benchmark
  • UniqueString100bytes (C++) with params=3, source=cpp-micro, suite=arrow-compute-vector-hash-benchmark
  • UniqueString100bytes (C++) with params=1, source=cpp-micro, suite=arrow-compute-vector-hash-benchmark
  • UniqueString100bytes (C++) with params=4, source=cpp-micro, suite=arrow-compute-vector-hash-benchmark