Thanks Michael, that sounds like it could be the reason for my issues. I assume that I could also build condor_gpu_discovery myself, linking against CUDA 10 to mitigate
the problem. Can you (or anyone) confirm this? On a slightly related note: I expected that I could use HTCondor 8.8’s gpu load monitoring to not only observe the gpu load created by the job, but also the overall
gpu load of the system (e.g. to modify my START _expression_ such that gpu jobs are only scheduled when no interactive gpu jobs are running). However, I cannot find any variables in my machine ads (and neither in the docs) to use for this. Is this kind of thing
supported at all? Thanks and best regards, Jens From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx]
On Behalf Of Michael Pelletier I think ran into this same problem with CUDA 10.0 in a recent 8.6 release, and I think it had something to do with a change to the interface between the 9.x and 10.0 CUDA libraries. It was giving some really
off-the-wall numbers to the collector. I believe there’s a ticket open for the issue as a result of my inquiry to support. In the meantime, you can also install the 9.2 release, and then set up the library path for condor_gpu_discovery to refer to /usr/local/cuda-9.2 instead of /usr/local/cuda, and that should get you through until
they come out with an update for CUDA 10 support. Michael V. Pelletier From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Jens Schmaler Dear all, we are using HTCondor 8.8 on Windows (Win 10 and Win 2016 specifically) with CUDA 10.0 installed. Some systems do have large GPUs, e.g. with 12 GB or even 32 GB of
memory. Nevertheless, condor_gpu_discovery will only show a maximum of Besides that, I discovered that condor_gpu_discovery tries to access the registry key
"SOFTWARE\\NVIDIA Corporation\\GPU Computing Toolkit\\CUDA" which does not seem to exist on any of our systems. Could you please tell me under which circumstances you would expect this key to exist? Thanks a lot, Jens |