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

Benchmarks with performance regressions

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

Benchmarks with regressions:

• Commit Run on ec2-m5-4xlarge-us-east-2 at 2023-09-25 19:11:51Z
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-15, scale_factor=10

All benchmark runs analyzed:

• Commit Run on ec2-t3-xlarge-us-east-2 at 2023-09-25 17:07:57Z
• Commit Run on arm64-t4g-linux-compute at 2023-09-25 19:44:04Z
• Commit Run on ec2-m5-4xlarge-us-east-2 at 2023-09-25 19:11:51Z
• Commit Run on arm64-m6g-linux-compute at 2023-09-25 22:49:45Z
• Commit Run on ursa-thinkcentre-m75q at 2023-09-26 01:23:47Z

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-09-26 01:23:47Z
  • BM_RleEncoding (C++) with params=1024/16, source=cpp-micro, suite=parquet-column-io-benchmark
  • BM_RleEncoding (C++) with params=32768/16, source=cpp-micro, suite=parquet-column-io-benchmark
  • BM_RleEncoding (C++) with params=4096/16, source=cpp-micro, suite=parquet-column-io-benchmark