try a disk cache using the restore_keys trick#16
Merged
Conversation
xvandish
added a commit
that referenced
this pull request
Jul 19, 2022
* try a disk cache using the restore_keys trick * now add a blank line to test rebuild with cache * print cache size * update actions/cache to v3 for perf improvments * remove useless ls * remove space * bump down to v2 until the max_length issue is resolved actions/toolkit#1030 * Attempt to fix images building on pr's to my_main * Add debugging step * Add cron schedule so github doesn't pruge cache, and remove debug step * Read-only cache on PR's again now that cache is seeded
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We just switched from BuildBuddy GRPC cache -> GCS HTTP cache, and now we're changing one more time to a "local" gh cache.
We use the
actions/cacheaction provided by GitHub to store the Bazel cache, along with arestore_keystrick that allows us to write to the cache on every invocation. Bazel builds now take ~30s for repeat builds, and the thing that's slowish is downloading/uploading the cache, which takes ~80% of the CI run time. But combined, the now ~4-5min CI times are much faster than the average remote cache run.