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

Benchmarks with performance regressions

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

All benchmark runs analyzed:

• Commit Run on amd64-c6a-4xlarge-linux at 2024-09-11 01:43:10Z
• Commit Run on arm64-t4g-2xlarge-linux at 2024-09-11 04:23:33Z
• Commit Run on amd64-m5-4xlarge-linux at 2024-09-11 06:55:42Z
• Commit Run on test-mac-arm at 2024-09-11 10:08:11Z

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 amd64-c6a-4xlarge-linux at 2024-09-11 01:43:10Z

  • TouchArea (C++) with params=size:16777216/real_time/threads:8, source=cpp-micro, suite=arrow-memory-pool-benchmark
  • BenchmarkTemporalBinary (C++) with params=<NanosecondsBetween, zoned>/524288/0, source=cpp-micro, suite=arrow-compute-scalar-temporal-benchmark
  • BenchmarkTemporalBinary (C++) with params=<SecondsBetween, zoned>/524288/0, source=cpp-micro, suite=arrow-compute-scalar-temporal-benchmark

• Commit Run on arm64-t4g-2xlarge-linux at 2024-09-11 04:23:33Z

  • BenchmarkBitmapVisitUInt8And (C++) with params=131072/0, source=cpp-micro, suite=arrow-bit-util-benchmark

• Commit Run on amd64-m5-4xlarge-linux at 2024-09-11 06:55:42Z

  • memory_latency (C++) with params=524288/repeats:1, source=cpp-micro, suite=arrow-machine-benchmark