Fixes
Fixes ranked by what your numbers show
Each bottleneck the analyzer detects, the rule that fires it, and the change that addresses it.
01
Undersized runner
Build and test dominate the job: the machine is the limit.
Runner options shownFires whenbuild + test ≥ 5 min and ≥ 60% of the job
ChangeMove the job to a bigger or faster runner
02Serial tests
One test step holds most of the job.
Runner options shownFires whentest ≥ 3 min, ≥ 40% of the job, one step ≥ 80% of test time
ChangeShard the suite across a job matrix
03Cold caches
Restoring and saving the cache costs more than it should.
Runner options shownFires whencache steps ≥ 30s or ≥ 10% of the job
ChangeKey the cache on the lockfile, with a fallback
04Slow installs
Dependency installs run from scratch every time.
Fires wheninstall ≥ 60s or ≥ 15% of the job
ChangeTurn on the setup action's built-in cache
05Queue wait
Jobs wait for a runner before any step starts.
Fires whenqueued ≥ 60s or ≥ 20% of the job
ChangeCancel superseded runs so they free runners
06Slow setup
Toolchains and containers are set up on every run.
Fires whensetup ≥ 60s or ≥ 15% of the job
ChangeRun the job in a prebuilt container
The order on this page is fixed. In the analyzer, fixes are ranked by the time your run spent in the phases each one addresses.