-
Notifications
You must be signed in to change notification settings - Fork 701
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
validate.sh: --jobs
should default to nproc
#10315
Conversation
I have 16 cores, but I also have quite a lot going on on my machine and would prefer validates not interfere. I think the idea of 4 is a reasonable default that can be overridden depending on environment. |
@geekosaur Sure, I don't think we should remove the |
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.
Seems like a reasonable default especially due to its wide adoption (from my experience). Thank you.
If `nproc` is available and `--jobs` is not given, this will use the output of `nproc` as the value for `--jobs`. Otherwise, the old default value of 4 will be used and a warning will be printed. The default value of 4 has remained unchanged since it was added in 6a9a101 in 2018; that may have been a reasonable number of cores then, but my development machine today has 20 cores, so setting the parallelism to 4 leaves a lot of performance on the table!
6b9bacf
to
00c9b65
Compare
@mergify backport 3.12 |
✅ Backports have been created
|
validate.sh: `--jobs` should default to `nproc` (backport #10315)
If
nproc
is available and--jobs
is not given, this will use the output ofnproc
as the value for--jobs
.Otherwise, the old default value of 4 will be used and a warning will be printed.
The default value of 4 has remained unchanged since it was added in 6a9a101 in 2018; that may have been a reasonable number of cores then, but my development machine today has 20 cores, so setting the parallelism to 4 leaves a lot of performance on the table!