Performance
Why does the Gradle daemon start every run?
Quick answer
Each CI job is a fresh machine, so there is no daemon to reuse — and without the configuration cache Gradle re-evaluates the whole build.
The detail that matters
Enable --configuration-cache and --build-cache. The daemon startup remains, but the expensive configuration phase does not.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
Why are GitHub Actions slow?Most commonly: shared vCPU, cold caches, network-attached disk, and queue time before the job even starts.How fast do runners start after a job is queued?runnerhut runners start in about three seconds from a warm pool.Do I need to change my workflow?No. Change the runs-on label and leave everything else as it is.How do I choose a runner size?Start one size above your current runner, then check CPU utilization and stop when the curve flattens.