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

Benchmarks with errors

These are errors that were caught while running the benchmarks. You can click each link to go to the Conbench entry for that benchmark, which might have more information about what the error was.

• Commit Run on ursa-i9-9960x at 2023-12-22 09:10:58Z
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-15, scale_factor=10

Benchmarks with performance regressions

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

All benchmark runs analyzed:

• Commit Run on ursa-i9-9960x at 2023-12-22 09:10:58Z
• Commit Run on ec2-t3-xlarge-us-east-2 at 2023-12-22 02:55:01Z
• Commit Run on arm64-t4g-linux-compute at 2023-12-22 02:33:50Z
• Commit Run on ec2-m5-4xlarge-us-east-2 at 2023-12-22 01:45:31Z
• Commit Run on arm64-m6g-linux-compute at 2023-12-22 05:32:34Z
• Commit Run on ursa-thinkcentre-m75q at 2023-12-22 17:13:12Z

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-12-22 17:13:12Z
  • ErrorSchemeBoolNoInline (C++) with source=cpp-micro, suite=arrow-type-benchmark