-
Notifications
You must be signed in to change notification settings - Fork 612
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
Dynamically detect CUDA availability #174
Comments
I think this is incorporated in the latest version of the library. |
This is done with #518 - and will be in the next release. Sorry for the delay in getting this in. The next release will also include some breaking API changes - and I'm wondering if this will affect the shims in lenskit ? #481 has details of the changes, but the big ones are that we're changing model.fit to take a user/items sparse matrix (instead of a item/users sparse matrix) and that we're also changing the return value type from the recommend/similar_items methods. |
@benfred thanks! In the next release of LensKit (0.14), I am splitting the various shims into their own packages (implicit's is here), which will hopefully ease maintenance a bit. Can update that so it uses 0.5 easily enough, I think. My only concern is that the current (and older) versions of LensKit don't have a max version bound on the |
It'd be useful in my environment to dynamically detect whether CUDA is actually available when Implicit has been built with CUDA.
Our cluster has some nodes with GPUs and some without. As it is, my experiment code has logic to detect which queue I submitted an experiment to and set
use_cuda
appropriately; falling back to non-CUDA operation (possibly with a warning?) if CUDA is compiled but not available at runtime would simplify driver code operating in heterogeneous environments.The text was updated successfully, but these errors were encountered: