-
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] GPU support #3776
Comments
Closing this, as we use #2302 to track feature requests. Leave a comment below if you'd like to contribute this feature, and we'll be happy to re-open it! |
…twork (fixes #3753) (#3766) * starting work * fixed port-binding issue on localhost * minor cleanup * updates * getting closer * definitely working for LocalCluster * it works, it works * docs * add tests * removing testing-only files * linting * Apply suggestions from code review Co-authored-by: Nikita Titov <nekit94-08@mail.ru> * remove duplicated code * remove unnecessary listen() Co-authored-by: Nikita Titov <nekit94-08@mail.ru>
Another action required to address this issue is bringing support of OpenCL-based GPU training or documenting why it can't be supported.
|
Summary
The Dask interface in https://github.com/microsoft/LightGBM/blob/706f2af7badc26f6ec68729469ec6ec79a66d802/python-package/lightgbm/dask.py currently only supports CPU-based training.
It should support GPU-based training as well, for those who want to use
lightgbm.dask
to perform multi-GPU training (dask/community#104 (comment)).Motivation
Adding this feature would allow users to use
lightgbm.dask
as a way to more easily perform multi-GPU training.Notes for Reviewers
This issue is intentionally vague on details, because "GPU support" could be done in different ways.
For example, we could consider allowing the Dask model objects to take in
dask-cudf
data frames iflightgbm
has been built with CUDA-based GPU support.References
This issue was originally posted as dask/dask-lightgbm#22, and more background is available there. Moving it here as part of dask/community#104.
The text was updated successfully, but these errors were encountered: