8000 Clarify n_jobs for gridsearch in docs · Issue #5797 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]

Skip to content

Clarify n_jobs for gridsearch in docs #5797

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

Closed
Korijn opened this issue Nov 12, 2015 · 2 comments · Fixed by #8106
Closed

Clarify n_jobs for gridsearch in docs #5797

Korijn opened this issue Nov 12, 2015 · 2 comments · Fixed by #8106
Labels
Documentation Easy Well-defined and straightforward way to resolve

Comments

@Korijn
Copy link
Korijn commented Nov 12, 2015

GridSearchCV's parameter n_jobs appears to indicate the amount of jobs that the work should be split up into, but it's actually the amount of jobs that can run in parallel. Looking at the docs for joblib's Parallel class, the explanation is much clearer than the one in sklearn's docs:

n_jobs: int, default: 1 :
The maximum number of concurrently running jobs, such as the number of Python worker processes when backend=”multiprocessing” or the size of the thread-pool when backend=”threading”. If -1 all CPUs are used. If 1 is given, no parallel computing code is used at all, which is useful for debugging. For n_jobs below -1, (n_cpus + 1 + n_jobs) are used. Thus for n_jobs = -2, all CPUs but one are used.

Can that be clarified in the docs?

@GaelVaroquaux
Copy link
Member
GaelVaroquaux commented Nov 12, 2015 via email

@Korijn
Copy link
Author
Korijn commented Nov 12, 2015

OK, I will!

@amueller amueller added Easy Well-defined and straightforward way to resolve Documentation Need Contributor labels Oct 27, 2016
accraze added a commit to accraze/scikit-learn that referenced this issue Dec 23, 2016
accraze added a commit to accraze/scikit-learn that referenced this issue Jan 1, 2017
accraze added a commit to accraze/scikit-learn that referenced this issue Jan 1, 2017
accraze added a commit to accraze/scikit-learn that referenced this issue Jan 2, 2017
accraze added a commit to accraze/scikit-learn that referenced this issue Jan 4, 2017
accraze added a commit to accraze/scikit-learn that referenced this issue Jan 4, 2017
accraze added a commit to accraze/scikit-learn that referenced this issue Jan 4, 2017
raghavrv pushed a commit to raghavrv/scikit-learn that referenced this issue Jan 5, 2017
sergeyf pushed a commit to sergeyf/scikit-learn that referenced this issue Feb 28, 2017
Sundrique pushed a commit to Sundrique/scikit-learn that referenced this issue Jun 14, 2017
NelleV pushed a commit to NelleV/scikit-learn that referenced this issue Aug 11, 2017
paulha pushed a commit to paulha/scikit-learn that referenced this issue Aug 19, 2017
maskani-moh pushed a commit to maskani-moh/scikit-learn that referenced this issue Nov 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Easy Well-defined and straightforward way to resolve
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
0