With all of our tests using t.Parallel() appropriately, we can leverage a larger runner to further cut down on how long our tests take.
Based on https://github.com/chainguard-dev/malcontent/pull/632, 8-core runners offer a sizable performance uplift over the default 4-core runners and anything larger hits the realm of diminishing returns pretty quickly.
This definitely beats the 12-13+ minute Workflow runs we were seeing originally.
Bonus third-party rule Workflow timing after the change (ten minutes faster!):
With all of our tests using
t.Parallel()
appropriately, we can leverage a larger runner to further cut down on how long our tests take.Based on https://github.com/chainguard-dev/malcontent/pull/632, 8-core runners offer a sizable performance uplift over the default 4-core runners and anything larger hits the realm of diminishing returns pretty quickly.
This definitely beats the 12-13+ minute Workflow runs we were seeing originally.
Bonus third-party rule Workflow timing after the change (ten minutes faster!):