Bridges-2 GPU

RP account needed

Bridges-2 GPU is the GPU-accelerated side of the Bridges-2 system at the Pittsburgh Supercomputing Center, with nodes aimed at deep learning, simulations, and other workloads that benefit from GPU acceleration.

It offers several GPU types, including the latest high-memory NVIDIA H100s, as well as L40S and V100 GPUs, which lets you match the hardware to the job. Jobs can use either full GPU nodes or, through a shared partition, just part of a node when fewer GPUs are needed. As an ACCESS-allocated resource, it is intended for researchers who need significant GPU capacity, alone or alongside traditional CPU computing.

Jobs

Jobs on Bridges-2's GPU nodes are submitted through the Slurm scheduler, using either the GPU or GPU-shared partition. Jobs in the GPU partition take one or more whole nodes, receiving all 8 GPUs on each (16 on the DGX-2). Jobs in the GPU-shared partition take up to half of a single node, between 1 and 4 GPUs, and share that node with other jobs.

Use sbatch to submit batch jobs and interact for interactive sessions. Either way, you specify the GPU type and count with --gpus=type:n or --gres=gpu:type:n, where the type is one of h100-80, l40s-48, v100-32, or v100-16. Note that n means the total GPUs for the job in batch mode (a multiple of 8), but GPUs per node in interactive mode (8, or 16 for the DGX-2).

Both partitions default to a 1-hour walltime, up to a 48-hour maximum. GPU-partition jobs are charged for the full node regardless of how many GPUs they use; GPU-shared jobs are charged only for the GPUs they request. Specific details are documented on the Accounting for Usage page on the Bridges-2 guide.

For more detail, please visit the Bridges-2 GPU and GPU-Shared partitions page or the Summary table for the GPU partition on the Bridges-2 guide.

A sample job script for the GPU partition would look like this:

#!/bin/bash
#SBATCH -N 1
#SBATCH -p GPU
#SBATCH -t 5:00:00
#SBATCH --gpus=v100-32:8

#type 'man sbatch' for more information and options
#this job will ask for 1 full v100-32 GPU node(8 V100 GPUs) for 5 hours
#this job would potentially charge 40 GPU SUs

#echo commands to stdout
set -x

# move to working directory
# this job assumes:
# - all input data is stored in this directory
# - all output should be stored in this directory
# - please note that groupname should be replaced by your groupname
# - PSC-username should be replaced by your PSC username
# - path-to-directory should be replaced by the path to your directory where the executable is

cd /ocean/projects/groupname/PSC-username/path-to-directory

#run pre-compiled program which is already in your project space

./gpua.out
 

After that, you need a sbatch command to submit a job to he GPU partition. A sample sbatch command to submit a job to the GPU partition to use 2 full GPU v100-16 nodes  and all 8 GPUs on each node for 5 hours is:

sbatch -p GPU -N 2 --gpus=v100-16:16 -t 5:00:00 jobname

where:

-p indicates the intended partition
-N 2 requests two v100-16 GPU nodes
--gpus=v100-16:16  requests the use of all 8 GPUs on both v100-16 nodes, for a total of 16 for the job
-t is the walltime requested in the format HH:MM:SS
jobname is the name of your batch script

Detailed information about batch jobs can be found in the Batch Jobs page of the guide.

Queue specifications

Metrics updated 2026-06-16

Name Purpose Nodes CPU cores / node GPUs / node Node RAM Jobs
30 days
Wait Time
30-day trend
Wall Time
30-day trend
GPU H100-80 Node. Accelerated workloads, deep learning, and GPU-intensive applications. 8 2x Intel Xeon "Sapphire Rapids" 8470 (52 cores) 8 NVIDIA H100-80GB SXM5 (80 GB vRAM) 2 TB 419
GPU wait time: average 119.4 hours, range 0 to 261.8 hours over 30 days
GPU wall time: average 3.4 hours, range 0.1 to 24 hours over 30 days
GPU-shared H100-80 Node. Accelerated workloads, deep learning, and GPU-intensive applications. 8 2x Intel Xeon "Sapphire Rapids" 8470 (52 cores) 8 NVIDIA H100-80GB SXM5 (80 GB vRAM) 2 TB 56,324
GPU-shared wait time: average 20.9 hours, range 2.3 to 88.1 hours over 30 days
GPU-shared wall time: average 2.5 hours, range 0.3 to 5.1 hours over 30 days
GPU L40S-48 Node. AI/ML, inference, fine-tuning, and mixed AI and visualization workloads. 3 2x Intel Xeon 6740E (96 cores) 8 NVIDIA L40S-48GB (48 GB vRAM) 1 TB 419
GPU wait time: average 119.4 hours, range 0 to 261.8 hours over 30 days
GPU wall time: average 3.4 hours, range 0.1 to 24 hours over 30 days
GPU-shared L40S-48 Node. AI/ML, inference, fine-tuning, and mixed AI and visualization workloads. 3 2x Intel Xeon 6740E (96 cores) 8 NVIDIA L40S-48GB (48 GB vRAM) 1 TB 56,324
GPU-shared wait time: average 20.9 hours, range 2.3 to 88.1 hours over 30 days
GPU-shared wall time: average 2.5 hours, range 0.3 to 5.1 hours over 30 days
GPU V100-32 Node. General GPU workloads and CUDA applications needing higher GPU memory. 24 2× Intel Xeon Gold 6248 "Cascade Lake" (40 cores) 8 NVIDIA Tesla V100-32GB SXM2 (32 GB vRAM) 512 GB 419
GPU wait time: average 119.4 hours, range 0 to 261.8 hours over 30 days
GPU wall time: average 3.4 hours, range 0.1 to 24 hours over 30 days
GPU-shared V100-32 Node. General GPU workloads and CUDA applications needing higher GPU memory. 24 2× Intel Xeon Gold 6248 "Cascade Lake" (40 cores) 8 NVIDIA Tesla V100-32GB SXM2 (32 GB vRAM) 512 GB 56,324
GPU-shared wait time: average 20.9 hours, range 2.3 to 88.1 hours over 30 days
GPU-shared wall time: average 2.5 hours, range 0.3 to 5.1 hours over 30 days
GPU V100-16 Node. GPU workloads with lower GPU-memory requirements. 9 2x Intel Xeon Gold 6148 (40 cores) 8 NVIDIA V100-16GB (16 GB vRAM) 192 GB 419
GPU wait time: average 119.4 hours, range 0 to 261.8 hours over 30 days
GPU wall time: average 3.4 hours, range 0.1 to 24 hours over 30 days
GPU-shared V100-16 Node. GPU workloads with lower GPU-memory requirements. 9 2x Intel Xeon Gold 6148 (40 cores) 8 NVIDIA V100-16GB (16 GB vRAM) 190 GB 56,324
GPU-shared wait time: average 20.9 hours, range 2.3 to 88.1 hours over 30 days
GPU-shared wall time: average 2.5 hours, range 0.3 to 5.1 hours over 30 days
GPU DGX-2 special node. Large single-node GPU jobs needing high GPU count on one node. 1 2× Intel Xeon Platinum 8168 (48 cores) 16 NVIDIA Volta V100-32GB (32 GB vRAM) 1500 GB 419
GPU wait time: average 119.4 hours, range 0 to 261.8 hours over 30 days
GPU wall time: average 3.4 hours, range 0.1 to 24 hours over 30 days
GPU-shared DGX-2 special node. Large single-node GPU jobs needing high GPU count on one node. 1 2× Intel Xeon Platinum 8168 (48 cores) 15 NVIDIA Volta V100-32GB (32 GB vRAM) 1500 GB 56,324
GPU-shared wait time: average 20.9 hours, range 2.3 to 88.1 hours over 30 days
GPU-shared wall time: average 2.5 hours, range 0.3 to 5.1 hours over 30 days

Software

The following software packages are among the most frequently used on Bridges-2 GPU, based on job data from XDMoD.

Most Frequently Used

Application Description Research Discipline Jobs
python Python is a high-level, interpreted programming language known for its simplicity and readability. It supports multiple programming paradigms and has a vast ecosystem of libraries and frameworks. Computer & Information Sciences, Software Engineering, Systems & Development 158,458
amber Amber is a suite of highly extensible molecular simulation programs. It is designed for simulations of biomolecules such as proteins, nucleic acids, and carbohydrates, and can also be used for small molecules. Biological Sciences 8,411
gromacs GROMACS (GROningen MAssive Parallel MD for Molecular Dynamics) is a versatile package for molecular dynamics simulations with a strong emphasis on high-performance computing capabilities. Biological Sciences 697
lammps LAMMPS (Large-scale Atomic/Molecular Massively Parallel Simulator) is a classical molecular dynamics code designed for simulating large-scale atomistic systems. It is highly versatile and can be used to model a wide range of materials and complex molecular structures. Chemical Sciences 154
r R is a free software environment for statistical computing and graphics. It compiles and runs on a wide variety of UNIX platforms, Windows, and MacOS. Computer Science 142
namd NAMD (NAnoscale Molecular Dynamics) is a parallel molecular dynamics code designed for high-performance simulation of large biomolecular systems. It is optimized for the simulation of biomolecular systems containing millions of atoms. Biochemistry and Molecular Biology 54
X11 applications 7
castro 3
charm++ 1
hh-suite HH-suite is a software package for sensitive protein sequence searching based on profile hidden Markov models. It includes tools for the alignment of protein sequences, detecting remote homologs, and predicting protein structures. Biological Sciences 1

Datasets

Name Description
2019nCoVR: 2019 Novel Coronavirus Resource

COVID-19 genomic surveillance data and metadata (hosted by NGDC).

Webpage: https://ngdc.cncb.ac.cn/ncov/?lang=en.
Path in Bridges-2: /ocean/datasets/community/alphafold.

AlphaFold

Predicted protein structures for the human proteome and other key proteins.

Webpage: https://alphafold.ebi.ac.uk/.
Path in Bridges-2: at /ocean/datasets/community/alphafold.

CIFAR-10

60,000 labeled images across 10 classes; standard image-classification benchmark.

Webpage: https://www.cs.toronto.edu/~kriz/cifar.html.Path in Bridges-2: /ocean/datasets/community/cifar.

COCO

Large-scale image dataset for object detection, segmentation, and captioning.

Webpage: https://cocodataset.org/.
Path in Bridges-2: /ocean/datasets/community/COCO.

CosmoFlow

~10,000 cosmological dark-matter simulations. Access requires a request via the CosmoFlow request form.

Webpage: https://portal.nersc.gov/project/m3363/.
Path in Bridges-2: /ocean/datasets/community/cosmoflow.

ImageNet

Image dataset organized by WordNet hierarchy.

Webpage: http://image-net.org/.
Path in Bridges-2: /ocean/datasets/community/imagenet.

MNIST

Classic handwritten-digit dataset for image-processing benchmarks.

Path in Bridges-2: /ocean/datasets/community/mnist.

Natural Languge Tool Kit Data

Corpora, grammars, and trained models for NLP.

Webpage: http://www.nltk.org/nltk_data/.
Path in Bridges-2: /ocean/datasets/community/nltk.

OpenWebText

Path in Bridges-2: /ocean/datasets/community/openwebtext.

PREVENT-AD

Longitudinal multimodal data from cognitively healthy older adults at risk for Alzheimer's, from two prevention trials.

Path in Bridges-2: /ocean/datasets/community/prevent_ad.

TCGA Images

Path in Bridges-2: /ocean/datasets/community/tcga_images.

Genomics datasets

These datasets are available to anyone with an allocation on Bridges-2. They are stored under /ocean/datasets/community/genomics.

AUGUSTUS, BLAST, CheckM, Dammit, Homer, Kraken2, Pfam, Prokka Repbase

 


Storage

File System

Directory Path Quota Purge Backup Notes
$HOME /jet/home/PSC-username 25 GB 3 months after allocation expires Daily
$PROJECT /ocean/projects/groupname/PSC-username 3 months after allocation expires None Quota size depends on allocation
$LOCAL Node-local (no global path) Immediately after job ends None Quota varies by node type
$RAMDISK Node memory (no filesystem path) Immediately after job ends None Quota depends on allocated node memory

File Transfer

A variety of transfer methods are available for Bridges-2. All transfers must be initiated from your local machine through the dedicated Data Transfer Node (data.bridges2.psc.edu) rather than the login nodes, to avoid disrupting interactive use. DTNs are specifically built to be high-speed data connectors. Use rsync, scp, or sftp for standard command-line transfers, or Globus for large datasets or transfers with many files, since it can automatically retry and resume after interruptions.

For more detail, please visit https://www.psc.edu/resources/bridges-2/user-guide#transferring-files and https://www.psc.edu/resources/bridges-2/user-guide#file-spaces.

Supported Methods Data Transfer Node URL
GLOBUS | RECOMMENDED PSC Bridges-2 /ocean and /jet filesystems https://app.globus.org
RSYNC data.bridges2.psc.edu
SCP data.bridges2.psc.edu
SFTP data.bridges2.psc.edu