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

Benchmarks with performance regressions

There weren't enough matching historic runs in Conbench to make a call on whether there were regressions or not.

To use the lookback z-score method of determining regressions, there need to be at least two historic runs on the default branch which, when compared to one of the runs on the contender commit, are on the same hardware, and have at least one of the same benchmark case and context pairs.

All benchmark runs analyzed:

• Commit Run on ursa-thinkcentre-m75q at 2024-05-23 03:01:46Z
• Commit Run on test-mac-arm at 2024-05-23 03:13:23Z
• Commit Run on ec2-m5-4xlarge-us-east-2 at 2024-05-23 02:32:56Z
• Commit Run on ec2-t3-xlarge-us-east-2 at 2024-05-23 03:45:53Z
• Commit Run on arm64-t4g-linux-compute at 2024-05-23 03:25:42Z
• Commit Run on arm64-m6g-linux-compute at 2024-05-23 02:16:01Z
• Commit Run on ursa-i9-9960x at 2024-05-23 03:38:47Z