-
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
GPU documentation is not clear #4467
Comments
@cookielee77 Thanks a lot for bringing this up!
Sure! Could you please suggest how these wordings can be improved to be clearer?
You can subscribe to the following GitHub issue to get all news about single-prevision mode with CUDA version. For now, no one have taken this feature request, unfortunately. |
@cookielee77 Yes, we have a plan to support single-precision calculation with CUDA in the very near future. |
hi,I would like to realize the difference between gpu version and cuda version, do you know where the doc is? @cookielee77 @jameslamb @StrikerRUS @shiyu1994 @cbecker |
@BinchaoPeng Hi! CUDA version is a re-written in CUDA language GPU version for systems where OpenCL is not available. |
okay,thank you! |
This issue has been automatically closed because it has been awaiting a response for too long. When you have time to to work with the maintainers to resolve this issue, please post a new comment and it will be re-opened. If the issue has been locked for editing by the time you return to it, please open a new issue and reference this one. Thank you for taking the time to improve LightGBM! |
This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Looks like "device=gpu" only supports single gpu training but "device=cuda" can support multi-gpus training. In addition, "cuda" looks like only support double-precision which is memory consuming.
Is it possible to update the documentation for GPU argument more clearer (it took me a lot of time to find these secrets)? Also, is there a plan to support the single-prevision calculation with CUDA version in the near future? Double-precision is super memory-costly.
Thanks!
The text was updated successfully, but these errors were encountered: