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

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 2023-08-09 06:06:47Z
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-07, scale_factor=1
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-07, scale_factor=1
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-01, scale_factor=1

All benchmark runs analyzed:

• Commit Run on ec2-m5-4xlarge-us-east-2 at 2023-07-30 21:58:11Z
• Commit Run on ec2-t3-xlarge-us-east-2 at 2023-07-30 22:48:34Z
• Commit Run on arm64-t4g-linux-compute at 2023-07-30 22:56:47Z
• Commit Run on arm64-m6g-linux-compute at 2023-07-30 22:48:21Z
• Commit Run on ursa-thinkcentre-m75q at 2023-07-31 01:41:23Z
• Commit Run on ursa-i9-9960x at 2023-08-09 06:06: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-i9-9960x at 2023-08-09 06:06:47Z
  • vectorFromArray (JavaScript) with from=booleans, source=js-micro