-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build cache for export step takes ~300s to complete #545
Comments
+1 trying to have a very fast build on the CI, and currently all time is spent preparing and exporting the cache ... |
@anthonyma94 @Tirke Hard to tell without a repro. Do you have a link to your repo? |
@crazy-max it's a private repo unfortunately. Maybe @Tirke can help on that front? |
I have the same issue, but I'm using https://github.com/ZcashFoundation/zebra/runs/5032296281?check_suite_focus=true#step:6:968 |
Related: #259 |
Have similar issue, but this might be caused by cache size Repro repo here, following jobs (clean runs, no previous cache):
I'm using |
@barthap This was my thinking too (external volume mount), theoretically that shouldn't be a problem or even difficult, but the question is how to turn off the cache export step. ETA: We use self-hosted Github Actions runners. |
Bumping this into 2023, not caching anything sucks and makes GHA much slower than just building locally. |
By switching to the S3 cache, I solved all my performance issues / cache limitations with Github Actions. |
In my case, it worked well to adjust the |
Yes you might hit GitHub rate-limit when pushing cache blobs to their backend which we don't control. You might also be interested in using |
I followed the docs here to use caching in my actions, but my job takes an extremely long time (300s on average) to prepare and export build cache to GitHub. Is there a reason the caching takes so long?
YAML file:
The text was updated successfully, but these errors were encountered: