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

Benchmarks with performance regressions

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

Benchmarks with regressions:

• Commit Run on ec2-m5-4xlarge-us-east-2 at 2024-02-05 19:34:29Z
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-03, scale_factor=10
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-01, scale_factor=10

All benchmark runs analyzed:

• Commit Run on ursa-i9-9960x at 2024-02-05 16:27:40Z
• Commit Run on ec2-t3-xlarge-us-east-2 at 2024-02-05 16:32:08Z
• Commit Run on ec2-m5-4xlarge-us-east-2 at 2024-02-05 19:34:29Z
• Commit Run on arm64-t4g-linux-compute at 2024-02-05 19:47:19Z
• Commit Run on ursa-thinkcentre-m75q at 2024-02-05 17:20:51Z

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 2024-02-05 17:20:51Z
  • CheckIndexBoundsUInt32 (C++) with params=524288/1, source=cpp-micro, suite=arrow-int-util-benchmark
  • Constants (C++) with source=cpp-micro, suite=arrow-decimal-benchmark
  • CheckIndexBoundsInt32 (C++) with params=524288/1, source=cpp-micro, suite=arrow-int-util-benchmark
  • CheckIndexBoundsUInt32 (C++) with params=32768/1, source=cpp-micro, suite=arrow-int-util-benchmark
  • CheckIndexBoundsInt32 (C++) with params=32768/1, source=cpp-micro, suite=arrow-int-util-benchmark