-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
fix: bounded parallelization when saving cache #723
fix: bounded parallelization when saving cache #723
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/vercel/turbo-site/6KYpyJf7wDUM1jM4BhPZqvXyByAh [Deployment for 3a4379d failed] |
7860a93
to
53e27c5
Compare
401c8fa
to
f804c14
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a much better approach!
I think the next step is to figure out how to thread a configuration value through to this point so that it can be customized.
76fa406
to
7a148dd
Compare
@gsoltis any chance we can get this merged without the configurable option? I understand a parameter would be good, but I feel it's best we fix the issue first. |
Cutting now |
Fix for #711 (discussion #709).
Bounded cache saving parallelization to
runtime.NumCPU()
which now gives us the maximum number of effective threads while staying under the OS limit of max processes count.Cheers 🎉