Guides
How to work around the 10 GB cache limit
Your caches exceed 10 GB per repository and start silently evicting.
5 min read
Your caches exceed 10 GB per repository and start silently evicting.
Why it happens
GitHub caps Actions cache at 10 GB and evicts least-recently-used entries once you cross it. Builds keep passing, they just get slower.
How to fix it
- Measure total cache size per repository before assuming you are under the cap
- Split caches so hot entries are not evicted by cold ones
- Compress with zstd rather than the default
- Move to a provider without a per-repository cap if you are structurally over it
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
How to make CI caches actually persistCaches are configured but hit rate is low.How to share a build cache across repositoriesEach repository maintains its own cache for the same shared dependencies.How to share a Docker cache between jobsEach matrix leg rebuilds the same layers.How to fix Docker cache invalidationDocker layers rebuild even when the relevant files did not change.