fix(cicd): experiment with using GHA cache with sccache#762
Open
chet wants to merge 1 commit intoNVIDIA:mainfrom
Open
fix(cicd): experiment with using GHA cache with sccache#762chet wants to merge 1 commit intoNVIDIA:mainfrom
chet wants to merge 1 commit intoNVIDIA:mainfrom
Conversation
🔐 TruffleHog Secret Scan✅ No secrets or credentials found! Your code has been scanned for 700+ types of secrets and credentials. All clear! 🎉 🕐 Last updated: 2026-03-31 20:38:26 UTC | Commit: 4db1036 |
4db1036 to
ebbe8a2
Compare
So I've been trying to figure out how to speed up build times, because they've gotten suuuper slow. One call out was we're not actually really using `sccache`, which I played around with in NVIDIA#733, but it didn't quite do what I wanted. I went this route because the default GHA cache size (if we wanted to use Github caching) is 10GB, unless you pay for more. So I had started an internal discussion (can't link it here), and I was pointed to some people who said we actually do pay for more GHA cache, meaning we CAN use it. That said, we may burn through our bumped up cache size pretty, quick, BUT, consider this an experiment. We want to see: - How quickly we burn through the cache. - If we see immediately noticable benefits. - What we're leaving on the table by not wiring up `sccache` to use a cache. Another catch 22 is this has to be merged for subsequent PRs to leverage it (I can't do an A/B like I did with Azure testing), so once this gets merged, I can watch subsequent PR performance to see if we're benefitting from it. Signed-off-by: Chet Nichols III <chetn@nvidia.com>
ebbe8a2 to
33241e4
Compare
Contributor
Author
|
lol -- and i'm getting an error message (same as docker/build-push-action#1485) |
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
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.
Description
So I've been trying to figure out how to speed up build times, because they've gotten suuuper slow. One call out was we're not actually really using
sccache, which I played around with in #733, but it didn't quite do what I wanted. I went this route because the default GHA cache size (if we wanted to use Github caching) is 10GB, unless you pay for more. So I had started an internal discussion (can't link it here), and I was pointed to some people who said we actually do pay for more GHA cache, meaning we CAN use it.That said, we may burn through our bumped up cache size pretty, quick, BUT, consider this an experiment. We want to see:
sccacheto use a cache.Another catch 22 is this has to be merged for subsequent PRs to leverage it (I can't do an A/B like I did with Azure testing), so once this gets merged, I can watch subsequent PR performance to see if we're benefitting from it.
Note that I do set specific "fallback" environment variables here too -- if for some reason there is an error using the GH cache,
sccachewill just skip using the cache, to allow the build to proceed (albeit without leveraging the GH cache).Signed-off-by: Chet Nichols III chetn@nvidia.com
Type of Change
Related Issues (Optional)
Breaking Changes
Testing
Additional Notes