Closed PidgeyBE closed 2 years ago
It's something we should add. I don't know how soon this can get done. @kenhester do you have any time to work on this ? If not, no worries.
I am working on sync'ing pynvml with nvml. I have sync'd the headers up to CUDA 11. I will work to timely implement the API changes, enhancements, and updates.
To answer directly, MIG support is a target feature to implement.
MIG functionality is being added to my branch. There are more functions to be implemented, but comments and issues welcome.
cc @drobison00
Note that #32 includes some MIG support. However, I do not personally have the proper resources for testing.
Thanks @rjzamora, we can test once it's ready.
The bindings are updated. Please confirm it addresses your issue.
The LocalCUDACluster bug will probably require a Dask-CUDA fix (since I believe MIG requires a slightly different NVML API)
MIG support is in, so I think this can be closed. The LocalCUDACluster
issue is being discussed in https://github.com/rapidsai/dask-cuda/issues/583 , and it seems that all NVML features required for that are available in latest PyNVML releases.
Dear
Pynvml is not in sync anymore with nvml. More specifically it is not possible to access the MIG APIs: https://docs.nvidia.com/deploy/nvml-api/group__nvmlMultiInstanceGPU.html#group__nvmlMultiInstanceGPU_1g15e07cc6230a2d90c5bc85de85261ef7
Would it be possible to add these?
BR, Pieterjan