-
Notifications
You must be signed in to change notification settings - Fork 31
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
Large cache takes a long time to inject/extract #13
Labels
Comments
@alex-statsig caching NPM modules usually negatively affects build performance, because you spend more time on extracting and saving cache back compared to just not using cache and simply downloading packages from npm registry each time. NPM modules consist from many files, that's why cache extraction/saving is expensive. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mostly a discussion point, but I've noticed large caches take a very long time to inject/extract. In my case, I have a 467MB cache of npm modules. This is downloaded from github's cache into the workflow runner in 8s, and thus is often worth caching for GH workflows. However, the injection step takes 53s. It seems like a lot of this time is transferring context, supposedly 1.8GB worth (taking 30s). I'm not sure if this is because the context is no longer zipped like when GH downloads it, or if something else is causing the 500MB to triple in size. The extraction step takes 2m56s. Happy to provide any logs as needed.
The text was updated successfully, but these errors were encountered: