More detailed information on system resources can be found on our Compute Resources page.
Containers with GPU Support
Singularity containers are available as modules on HPC for GPU-supported workflows. For more information, see our documentation on Containers.
Information on how to request GPUs using SLURM can be found in our SLURM Documentation.
For a list of training resources related to GPU workflows, see our Training documentation.
Puma has a different arrangement for GPU nodes than Ocelote and ElGato. Whereas the older clusters have one GPU per node, Puma has four. This has a financial advantage for providing GPU's with lower overall cost, and a technical advantage of allowing jobs that can use multiple GPU's to run faster than spanning multiple nodes. This capability comes from using a newer operating system.
Each node has four Nvidia V100S model GPUs. They are provisioned with 32GB memory compared to 16GB on the P100's.
Ocelote has 45 compute nodes with Nvidia P100 GPUs that are available to researchers on campus. There will be fairshare limitations but the intention is for them to be as widely available as possible. There are still compute nodes on El Gato with 70 nodes provisioned with Nvidia Tesla K20's.
The latest Cuda modules available on Ocelote are 9.0 and 9.1. Cuda 7.5 and 8.0 are still available.
The Cuda driver version on each P100 is 396.44
. The limitation is a maximum of 10 concurrent jobs. One node with a V100 is also available. Since there is only one, you can feel free to use it for testing and comparisons to the P100, but production work should be run on the P100's. There is also one node with two P100's for testing jobs that use two GPU's. This one should be used to compare with running a job on two nodes.
Nvidia Nsight Compute (the interactive kernel profiler) is not available. In response to a security alert (CVE-2018-6260) this capability is only available with root authority which users do not have.
The latest Cuda module available on the system is 11.0 and is the only version until newer ones come along. The Cuda driver version can be queried with the
nvidia-smi command. To see the modules available, in an interactive session simply run:
$ module avail cuda -------------------- /opt/ohpc/pub/moduledeps/gnu8-openmpi3 -------------------- cp2k-cuda/7.1.0 -------------------------- /opt/ohpc/pub/modulefiles --------------------------- cuda11-dnn/8.0.2 cuda11-sdk/20.7 cuda11/11.0
The OpenACC API is a collection of compiler directives and runtime routines that allow you to specify loops and regions of code in standard C, C++, and Fortran that you can offload from a host CPU to the GPU.
We provide two methods of support for OpenACC
- We support OpenACC in the PGI Compiler. The PGI implementation of OpenACC is considered the best implementation.
"module load pgi" on Ocelote. If you are on a GPU node from an interactive session you can run "pgaccelinfo" to test functionality. Remember that the login nodes do not have GPUs or software installed.
A useful getting-started guide written by Nvidia is atavailable here:
- We support OpenACC in the GCC Compiler 6.1 which is automatically loaded as a module when you log ininto Ocelote. Verify with "module list".
The GCC 6 release includes a much improved implementation of the OpenACC 2.0a specification.
A useful quick reference guide can be found at:
is available from: https://gcc.gnu.org/wiki/OpenACC#Quick_Reference_Guide
Many applications have been optimized to run faster on GPU's. These include:
|Installed as a module|
|A restricted license version is installed|
|; only available to|
|Installed as a module|
|Installed as a module|
|Installed as a module|
|and available as an application through Open OnDemand|
NVIDIA GPU Cloud Container Registry
We support the use of HPC and ML/DL containers available on NVIDIA GPU Cloud (NGC). Many of the popular HPC applications including NAMD, LAMMPS and GROMACS containers are optimized for performance and available to run in Singularity on Ocelote.
The containers and respective README files can be found at /unsupported/singularity/nvidia
NGC also provides a set of popular ML and DL frameworks which is not a trivial task. They have made them available to us and they will be updated regularly. They are currently located at: /unsupported/singularity/nvidia
The Nvidia images at /unsupported/singularity/nvidia have been modified to include bindings for your /extra and /rsgrps directories if you want to run you jobs from those directories.
PyTorch is a Python package that provides two high-level features:
- Tensor computation (like numpy) with strong GPU acceleration
- Deep Neural Networks built on a tape-based autograd system
|Installed as a module. See these notes.|
|MATLAB||Installed as a module and available as an application through Open OnDemand. Review the GPU Coder on their website|
|ANSYS Fluent||Installed as a module and available as an application through Open OnDemand|
|RELION||Available as a Singularity container or as a module.|
|ML and DL Frameworks||See the section below.|
Python ML/DL including Nvidia RAPIDS
The minimum version of Python that is supported is 3.6:Nvidia periodically runs training sessions like these ones:
Accelerate Your Code with OpenACC
|numba||RAPIDS: numba is for Cuda programming|
|cuml||RAPIDS: Cuda Machine Learning has many ML algorithms like K-means, PCA and SVM|
|cudf||RAPIDS: Cuda Dataframes supports loading and manipulating datasets|
|tensorflow||TensorFlow is an open source software library for numerical computation using data flow graphs.|
|torch||PyTorch supports tensor computation and deep neural networks|
Each is provided in a Singularity container.
The file name has a tag at the end that represents when it was made, so 18.01 is January 2018
Pulling Nvidia ML / DL Images on Ocelote
It is possible for you to create your own Singularity containers on Ocelote pulling down the images created by Nvidia. The general rule that you cannot create your own containers because that would require root authority still applies. Root authority is not required if you follow this procedure.
The GPU nodes have more memory than the other Ocelote nodes so the select statements reflect 8GB per core by 28 cores equals 224GB
Either: copy the file you wish to use to your directory. Your home path as well as /extra and /xdisk have been bound to the image, so those are your choices.
Or: run the singularity file from where it is. Since you cannot modify it you will not interfere with anyone else.
For interactive use, start an interactive job on a GPU node modifying this command:
$ qsub -I -N jobname -W group_list=GROUP-NAME -q windfall -l select=1:ncpus=28:mem=224gb:np100s=1 -l cput=1:0:0 -l walltime=1:0:0
You must change the group_list and you should change the other attributes as desired.
On the compute node assigned to you, as an example you can run:
$ module load singularity $ singularity exec --nv nvidia-tensorflow.18.01-py3.simg python tensorflow_example.py
You need to include the --nv and note it has two dashes. This will bind the Cuda libraries.
The example file is included in this directory. "tensorflow_example.py"
For batch use, you will include these three lines in your submission script
#PBS -l select=1:ncpus=28:mem=224gb:np100s=1 module load singularity singularity exec --nv nvidia-tensorflow.18.01-py3.simg python tensorflow_example.py
You will want exclusive access to the node so there is not contention for the GPU. That is obtained by asking for all 28 cores as shown above
There are more detailed examples here
For more information on Singularity, see their web site at:
There are tutorials for Singularity on HPC here
We host workshops from the Pittsburgh Supercomputer Center which is a NSF funded location. We are working with Nvidia to offer a workshop in the April 2018 timeframe.
Watch for announcements from the hpc-info list.
|caffe2||A deep learning framework|
|tensorrt||Inference server for deep learning|
|tensorboard||Visualization tool for machine learning|