Output GPU-related ClassAd attributes
condor_gpu_discovery [<options> ]
condor_gpu_discovery outputs ClassAd attributes corresponding to a host’s GPU capabilities. It can presently report CUDA and OpenCL devices; which type(s) of device(s) it reports is determined by which libraries, if any, it can find when it runs; this reflects what GPU jobs will find on that host when they run. (Note that some HTCondor configuration settings may cause the environment to differ between jobs and the HTCondor daemons in ways that change library discovery.)
GPU_DEVICE_ORDINAL is set in the
environment when condor_gpu_discovery is run, it will report only
devices present in the those lists.
This tool is not available for MAC OS platforms.
With no command line options, the single ClassAd attribute
DetectedGPUs is printed. If the value is 0, no GPUs were detected.
If one or more GPUS were detected, the value is a string, presented as a
comma and space separated list of the GPUs discovered, where each is
given a name further used as the prefix string in other attribute
names. Where there is more than one GPU of a particular type, the
prefix string includes an GPU id value identifying the device; these
can be integer values that monotonically increase from 0 when the
option is used or globally unique identfiers when the
-uuid argument is used.
For example, a discovery of two GPUs with
Further command line options use
"CUDA" either with or without one
of the integer values 0 or 1 as the prefix string in attribute names.
For machines with more than one or two NVIDIA devices, it is recommended that you
also use the
-uuid option. The uuid value assigned by
NVIDA to each GPU is unique, so using this option provides stable device
identifiers for your devices. The
-short-uuid option uses only part of the
uuid, but it is highly likely to still be unique for devices on a single machine.
As of HTCondor 9.0
-short-uuid is the default.
-short-uuid is used, discovery of two GPUs may look like this
Any NVIDIA runtime library later than 9.0 will accept the above identifiers in the
CUDA_VISIBLE_DEVICES environment variable.
If the NVML libary is available, and a multi-instance GPU (MIG) -capable
device is present, has MIG enabled, and has created compute instances
for each MIG instance, condor_gpu_discovery will report those instance
as distinct devices. Their names will be in the long UUID form unless
-short-uuid option is used, because they can not be enumerated
via CUDA. MIG instances don’t have some of the properties reported by
-dynamic options; these properties
will be omitted. If MIG is enabled on any GPU in the system, some properties
become unavailable for every GPU in the system; condor_gpu_discovery
will report what it can.
Print usage information and exit.
In addition to the
DetectedGPUsattribute, display some of the attributes of the GPUs. Each of these attributes will have a prefix string at the beginning of its name. The displayed CUDA attributes are
RuntimeVersion. The displayed Open CL attributes are
Display more attributes of the GPUs. Each of these attribute names will have a prefix string at the beginning of its name. The additional CUDA attributes are
CoresPerCU. The additional Open CL attributes are
Display attributes of NVIDIA devices that change values as the GPU is working. Each of these attribute names will have a prefix string at the beginning of its name. These are
When displaying attribute values, assume that the machine has a heterogeneous set of GPUs, so always include the integer value in the prefix string.
- -device <N>
Display properties only for GPU device <N>, where <N> is the integer value defined for the prefix string. This option may be specified more than once; additional <N> are listed along with the first. This option adds to the devices(s) specified by the environment variables
GPU_DEVICE_ORDINAL, if any.
- -tag string
Set the resource tag portion of the intended machine ClassAd attribute
Detected<ResourceTag>to be string. If this option is not specified, the resource tag is
"GPUs", resulting in attribute name
- -prefix str
When naming attributes, use str as the prefix string. When this option is not specified, the prefix string is either
-short-uuidis also used.
Use the prefix and device index as the device identifier.
Use the first 8 characters of the NVIDIA uuid as the device identifier. When this option is used, devices will be shown as
GPU-<xxxxxxxx>where <xxxxxxxx> is the first 8 hex digits of the NVIDIA device uuid. Unlike device indices, the uuid of a device will not change of other devices are taken offline or drained.
Use the full NVIDIA uuid as the device identifier rather than the device index.
For testing purposes, assume that N devices of type D were detected. No discovery software is invoked. If D is 0, it refers to GeForce GT 330, and a default value for N is 1. If D is 1, it refers to GeForce GTX 480, and a default value for N is 2.
Prefer detection via OpenCL rather than CUDA. Without this option, CUDA detection software is invoked first, and no further Open CL software is invoked if CUDA devices are detected.
Do only CUDA detection.
For Windows platforms only, use a CUDA driver rather than the CUDA run time.
Output in the syntax of HTCondor configuration, instead of ClassAd language. An additional attribute is produced
NUM_DETECTED_GPUswhich is set to the number of GPUs detected.
- -repeat [N]
Repeat listed GPUs N (default 2) times. This results in a list that looks like
CUDA0, CUDA1, CUDA0, CUDA1.
When repeating GPUs, repeat each GPU N times, not the whole list. This results in a list that looks like
CUDA0, CUDA0, CUDA1, CUDA1.
This option suppresses the
DetectedGpusattribute so that the output is suitable for use with condor_startd cron. Combine this option with the -dynamic option to periodically refresh the dynamic Gpu information such as temperature. For example, to refresh GPU temperatures every 5 minutesuse FEATURE : StartdCronPeriodic(DYNGPUS, 5*60, $(LIBEXEC)/condor_gpu_discovery, -dynamic -cron)
For interactive use of the tool, output extra information to show detection while in progress.
Show diagnostic information, to aid in tool development.
condor_gpu_discovery will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.