You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not an expert in this area, but I think it's counter-productive to set the concurrency to a higher number than there are CPU cores available for CPU-hungry processes, like tests and builds, as these processes would be competing for resources.
Thus, a default setting of 10 might be counter-productive in certain environments, like CI, where the number of cores can be lower.
For example, GitHub Actions only have 2 cores available for Windows and Linux, yet 3 for macOS.
Describe the solution you'd like
I think there should be a way to specify "max" or some other variation of that, that signals Turbo to sniff out the number of cores and set the concurrency to that value.
Describe alternatives you've considered
turbo run build --concurrency=$(node -r os -e 'process.stdout.write(os.cpus().length.toString())')