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

Benchmarks with performance regressions

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

Benchmarks with regressions:

• Commit Run on amd64-m5-4xlarge-linux at 2025-01-12 09:22:04Z
  • partitioned-dataset-filter (R) with dataset=dataset-taxi-parquet, language=R, query=vignette

All benchmark runs analyzed:

• Commit Run on amd64-m5-4xlarge-linux at 2025-01-12 09:22:04Z
• Commit Run on test-mac-arm at 2025-01-12 15:04:40Z
• Commit Run on amd64-c6a-4xlarge-linux at 2025-01-09 14:43:40Z
• Commit Run on arm64-t4g-2xlarge-linux at 2025-01-12 20:06:21Z

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-t4g-2xlarge-linux at 2025-01-12 20:06:21Z
  • BenchmarkTemporalRounding (C++) with params=<CeilTemporal, non_zoned, round_1_month>/1048576/0, source=cpp-micro, suite=arrow-compute-scalar-temporal-benchmark