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

Benchmarks with performance regressions

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

Benchmarks with regressions:

• Commit Run on ursa-i9-9960x at 2024-04-18 00:21:10Z
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-20, scale_factor=1
  • dataframe-to-table (R) with dataset=type_integers, language=R
  • dataframe-to-table (R) with dataset=type_floats, language=R

All benchmark runs analyzed:

• Commit Run on ec2-t3-xlarge-us-east-2 at 2024-04-17 05:23:45Z
• Commit Run on test-mac-arm at 2024-04-17 10:47:37Z
• Commit Run on ursa-thinkcentre-m75q at 2024-04-17 07:59:36Z
• Commit Run on ursa-i9-9960x at 2024-04-18 00:21:10Z
• Commit Run on ec2-m5-4xlarge-us-east-2 at 2024-04-17 09:43:59Z
• Commit Run on arm64-t4g-linux-compute at 2024-04-17 08:08:24Z
• Commit Run on arm64-m6g-linux-compute at 2024-04-17 19:16:05Z

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 test-mac-arm at 2024-04-17 10:47:37Z

  • ArrayRangeEqualsFloat32 (C++) with params=65536/100, source=cpp-micro, suite=arrow-compare-benchmark

• Commit Run on ursa-thinkcentre-m75q at 2024-04-17 07:59:36Z

  • BM_PlainEncodingBoolean (C++) with params=4096, source=cpp-micro, suite=parquet-encoding-benchmark