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

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-24 17:21:34Z
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-05, scale_factor=1
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-11, scale_factor=1
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-05, scale_factor=1
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-11, scale_factor=1

All benchmark runs analyzed:

• Commit Run on ursa-thinkcentre-m75q at 2023-08-25 12:42:41Z
• Commit Run on arm64-m6g-linux-compute at 2023-08-24 18:00:25Z
• Commit Run on ec2-t3-xlarge-us-east-2 at 2023-08-24 03:21:27Z
• Commit Run on ec2-m5-4xlarge-us-east-2 at 2023-08-24 06:51:23Z
• Commit Run on arm64-t4g-linux-compute at 2023-08-24 07:35:49Z
• Commit Run on ursa-i9-9960x at 2023-08-24 17:21:34Z

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-25 12:42:41Z
  • ValidateSmallAscii (C++) with source=cpp-micro, suite=arrow-utf8-util-benchmark