Caching
Why is cache restore slow?
Quick answer
GitHub throttles cache bandwidth, so a multi-gigabyte cache can take minutes to restore.
The detail that matters
Restore speed matters as much as hit rate. A cache that takes four minutes to restore and saves three is a net loss.
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 does Cargo rebuild everything?Your cache key changes on every run, or target/ is not cached at all.How do I write a good cache key?Hash exactly the files that determine the cached content — usually the lockfile — and nothing else.What are restore-keys?Ordered prefixes tried when the exact cache key misses, so a partial match can still be restored.Why does my cache miss every run?The key includes something that changes every run — commonly github.sha or a timestamp.