Skip to content
Latchkey LogoLatchkey home
EnglishPortuguês日本語
Start Free

Latchkey Learn

Faster GitHub Actions

Why Actions workflows are slow and the changes that make them fast, with numbers: caching, parallelism, cold starts and Docker build speed.

Start here four stops, in order

  1. 01Cache Rust and CargoCaching
  2. 02Matrix strategy and parallel jobsParallelism
  3. 03Run Actions on ARMCold start and checkout
  4. 04actions/cache vs buildx cacheDocker build speed

Contents 4 sections · 27 entries

Cold start and checkout 4 entries

Setup time, clones, runner size.

  1. 3.1Run Actions on ARM
  2. 3.2Reduce checkout time
  3. 3.3Choose a runner size
  4. 3.4Cold start and setup time
Explore other topics
GitHub Actions runners comparedEvery managed runner vendor, priced and benchmarked side by side. GitHub Actions costWhat Actions really costs, and how to cut it. Runner failures Latchkey repairsOut of memory, disk full, rate limits, lost runners: reproduced and fixed. GitHub Actions workflow errorsWorkflow, YAML, permissions and artifact errors, diagnosed and fixed. Docker in CI: Registry, Build & RuntimeRegistry, runtime and build errors on CI runners. CI for coding agentsGive your coding agent a runner.