Skip to content

[MRG] ENH add option to set the number of OpenMP threads in HistGBDT #16070

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
wants to merge 14 commits into from

Conversation

glemaitre
Copy link
Member

@glemaitre glemaitre commented Jan 9, 2020

closes #16016

Add a n_jobs parameter to set the number of threads (OpenMP threads) to be used when finding split. By default, we limit to 16 threads to avoid oversubscription issue.

@glemaitre glemaitre changed the title ENH add option to set the number of OpenMP threads in HistGBDT [WIP] ENH add option to set the number of OpenMP threads in HistGBDT Jan 9, 2020
@glemaitre glemaitre changed the title [WIP] ENH add option to set the number of OpenMP threads in HistGBDT [MRG] ENH add option to set the number of OpenMP threads in HistGBDT Jan 9, 2020
@glemaitre
Copy link
Member Author

ping @ogrisel @NicolasHug @jeremiedbb I think that this could be a draft to check if it was what you had in mind.

@glemaitre
Copy link
Member Author

To be in line with #14265, we could avoid exposing (n_threads).

@NicolasHug NicolasHug closed this Jan 9, 2020
@NicolasHug NicolasHug reopened this Jan 9, 2020
@NicolasHug
Copy link
Member

Sorry, didn't mean to close.

Indeed the parameter should not be exposed. We should only use _openmp_effective_n_threads with the default (None).

As documented in #15116, users should use OMP_NUM_THREADS

@glemaitre
Copy link
Member Author

Indeed the parameter should not be exposed. We should only use _openmp_effective_n_threads with the default (None).

I am fine with this. @NicolasHug could you comment on the original issue to know why @ogrisel wanted to expose it.

@glemaitre
Copy link
Member Author

OK so it should be really [MRG] now. @NicolasHug do you want to have a look.
@jeremiedbb maybe as well.

@glemaitre
Copy link
Member Author

@NicolasHug I remove the fixture

@NicolasHug
Copy link
Member

@glemaitre what's the status of this PR? It currently adds a n_threads param but we haven't decided on that yet

@glemaitre
Copy link
Member Author

glemaitre commented Feb 23, 2020 via email

@NicolasHug
Copy link
Member

So this is stalled? Should we tag with "Needs Bencmarks"?

@glemaitre
Copy link
Member Author

glemaitre commented Feb 23, 2020 via email

@NicolasHug
Copy link
Member

I mean, we do have the tag.

I'm trying to keep other reviewers from needlessly spending time reviewing the PR

@NicolasHug NicolasHug assigned NicolasHug and unassigned NicolasHug Feb 23, 2020
@NicolasHug NicolasHug added the Needs Benchmarks A tag for the issues and PRs which require some benchmarks label Feb 23, 2020
@glemaitre
Copy link
Member Author

Oh good I did not know that we add a tag. Thanks.

Base automatically changed from master to main January 22, 2021 10:51
@ogrisel
Copy link
Member

ogrisel commented Jan 25, 2022

I believe this was fixed concurrently in #20477. Let's close.

@ogrisel ogrisel closed this Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cython module:ensemble module:utils Needs Benchmarks A tag for the issues and PRs which require some benchmarks
Projects
None yet
4 participants