GPU clusters

From MetaCentrum
Jump to navigation Jump to search

(Česká verze)

Metacentrum wiki is deprecated after March 2023
Dear users, due to integration of Metacentrum into (e-INFRA CZ service), the documentation for users will change format and site.
The current wiki pages won't be updated after end of March 2023. They will, however, be kept for a few months for backwards reference.
The new documentation resides at

To write GPU accelerated programs, one will need to be familiar with high-level programming languages. Most GPU programming is based on the C language and its extensions. In the wider context, having a background in parallel computing techniques (threading, message passing, vectorization) will help one understand and apply GPU acceleration.

GPU clusters in MetaCentrum
Cluster Nodes GPUs per node Memory MiB compute capability CuDNN gpu_cap= - 4x A40 45 634 8.6 YES cuda35,cuda61,cuda75,cuda80,cuda86 - 1x A40 45 634 8.6 YES cuda35,cuda61,cuda75,cuda80,cuda86 - 8x RTX A4000 16 117 8.6 YES cuda35,cuda61,cuda75,cuda80,cuda86 1x A10 22 731 8.6 YES cuda35,cuda61,cuda75,cuda80,cuda86 - 4x A100 40 536 8.0 YES cuda35,cuda61,cuda75,cuda80 - 8x Quadro RTX 5000 16 125 7.5 YES cuda35,cuda61,cuda75 8x GeForce RTX 2080 Ti 11 019 7.5 YES cuda35,cuda61,cuda75 - 2x GeForce RTX 2080 Ti 11 019 7.5 YES cuda35,cuda61,cuda75 - 2x Tesla T4 15 109 7.5 YES cuda35,cuda61,cuda75 - 2x GeForce RTX 2080 7 982 7.5 YES cuda35,cuda61,cuda75 1x TITAN V GPU 12 066 7.0 YES cuda35,cuda61,cuda70 - 4x GeForce GTX 1080 Ti 11 178 6.1 YES cuda35,cuda61 - 2x 1080Ti GPU 11 178 6.1 YES cuda35,cuda61 1x GeForce GTX 1070 8 119 3.5 YES cuda35, cuda61 4x Tesla P100 16 280 6.0 YES cuda35, cuda60 2x Tesla P100 12 198 6.0 YES cuda35, cuda60 1x Tesla K40c 11 441 3.5 YES cuda35

Submitting GPU jobs

  • GPU queues: gpu (24 hours max) and gpu_long (up to 336 hours), both with open access for all MetaCentrum members
  • GPU jobs on the konos cluster can be also run via the priority queue iti (queue for users from ITI - Institute of Theoretical Informatics, Univ. of West Bohemia)
  • zubat cluster is available for any job which will run 24 hours at most.
  • Users from CEITEC MU and NCBR can run jobs via privileged queues on the zubat cluster.

  • The current version of the cuda drivers (parameter cuda_version) can be verified interactively in the qsub command assembler.

Requesting GPUs

The key scheduling constraint is to prevent jobs from sharing GPUs. To ensure this always use the gpu=X flag in qsub and request one of the gpu queues (gpu, gpu_long, iti).

qsub -l select=1:ncpus=1:mem=10gb:ngpus=X -q gpu

where X means a number of GPU cards required. By default


If a job requires more GPU cards than it asks (or is available), prolog does not run it.

To plan your job on clusters with certain compute capability, use qsub command like this:

qsub -q gpu -l select=1:ncpus=1:ngpus=X:gpu_cap=cuda35 <job batch file>

Using the PBS parameter gpu_mem is possible to specify the minimum amount of memory that the GPU card will have.

qsub -q gpu -l select=1:ncpus=1:ngpus=1:gpu_mem=10gb ...


qsub -I -q gpu -l select=1:ncpus=1:ngpus=1:scratch_local=10gb:gpu_mem=10gb -l walltime=24:0:0

Interactive job requests 1 machine, 1 CPU and 1 GPU card for 24 hours.


Q: How can I recognize which GPUs are reserved for me by planning system?

A: IDs of GPU cards are stored in CUDA_VISIBLE_DEVICES variable. These IDs are mapped to CUDA tools virtual IDs. Though if CUDA_VISIBLE_DEVICES contains value 2, 3 then CUDA tools will report IDs 0, 1.

Q: I want to use the NVIDIA CuDNN library, which GPU clusters do support it?

A: Those which have GPU with compute capability > 3.0, which means all clusters (see the table above)