-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[dask] allow customization of num_threads #3714
Comments
Closing this in favor of being in #2302 with other features. Please leave a comment here if you'd like to work on it. |
I'm going to open this because I'm actively working on it. @guolinke could you tell me more about this note in the parameter docs for https://lightgbm.readthedocs.io/en/latest/Parameters.html#num_threads
I'm wondering if this means that I should change the default behavior of the Dask module to use |
Just want to make sure you're aware of that Here are two examples where users are not happy with the default values: |
I'm going to close this again for now, currently focusing on other Dask items. This can be done after 3.2.0 (#3872 ). |
Related: dmlc/xgboost#7337. |
The following code of |
Summary
LightGBM training with Dask currently ignores the
num_threads
setting in user-provided parameters, and overwrites it with the number of CPU cores on each worker contributing to training.This behavior is a good default, but it should be possible to override it.
Motivation
There might be cases where it's desirable not to use as many threads as cores on each worker during training, and that should be possible.
References
LightGBM/python-package/lightgbm/dask.py
Line 144 in aae4fe4
This behavior was recommended in #3515 (comment).
The text was updated successfully, but these errors were encountered: