chore(ci): Restrict use of rust-cache to longest-running jobs #3277
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Spin CI currently always exceeds the 10GB cache quota. That means that between creating a cache entry and trying to use it, it has pretty much always been LRU evicted, so we pay for creating the entries, and never benefit from them. Or rather, that would be the situation if GitHub strictly enforced the cache limits. They apparently are planning on doing so starting in mid-October. Currently, we sometimes get eviction before any use, sometimes not. This change makes it so that only the two longest-running jobs use the cache, and that it's only saved on `main`. In combination, we should get much better hit rates for those two jobs, which should hopefully mean that CI most of the time completes in a bit more than 30 minutes, instead of frequently taking close to an hour. Signed-off-by: Till Schneidereit <[email protected]>
vdice
approved these changes
Sep 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spin CI currently always exceeds the 10GB cache quota. That means that between creating a cache entry and trying to use it, it has pretty much always been LRU evicted, so we pay for creating the entries, and never benefit from them.
Or rather, that would be the situation if GitHub strictly enforced the cache limits. They apparently are planning on doing so starting in mid-October. Currently, we sometimes get eviction before any use, sometimes not.
This change makes it so that only the two longest-running jobs use the cache, and that it's only saved on
main. In combination, we should get much better hit rates for those two jobs, which should hopefully mean that CI most of the time completes in a bit more than 30 minutes, instead of frequently taking close to an hour.