SLURM Partition Limits¶

Jobs can run on specific HiPerGator servers or nodes based on hardware requirements. Different sets of hardware configurations are presented as SLURM partitions. Also see: Available Node Features

Time Limits¶

Partitions have individual time limits. Example of time limit configuration:

SBATCH --time=4-00:00:00 # Walltime in hh:mm:ss or d-hh:mm:ss

Interactive Work¶

Partitions: hpg-dev, gpu, hpg-ai¶

Default time limit if not specified: 10 min

hpg-dev¶

Maximum: 12 hours

gpu¶

Maximum: 12 hours for srun .... --pty bash -i sessions
Maximum: 72 hours for Jupyter sessions in Open OnDemand.

hpg-ai¶

Maximum: 12 hours for srun .... --pty bash -i sessions

Jupyter¶

JupyterHub: Sessions are preset with individual limits shown in the menu
JupyterLab in Open OnDemand Maximum: 72 hours for the GPU partition, other partitions follow standard partition limits

GPU/HPG-AI Partitions¶

Default: 10 min
Maximum: 14 days

There is no burst QOS for the gpu partitions.

Note

The change from 7 to 14 days may be temporary. Our analysis of GPU usage patterns allows us to increase the maximum job time limit from the previous value of 7 days to the current value of 14 days. But if the resource utilization will approach levels that would prevent our ability to satisfy the investment QOS SLA, the time limit will be adjusted downwards to prevent service level degradation.

Compute Partitions¶

Partitions: hpg-default, hpg2-compute, bigmem¶

Both the hpg-default and the hpg2-compute partitions are selected by default if no partition is specified for a job.

Investment QOS¶

Default: 10 min
Maximum: 31 days (744 hours)

Burst QOS¶

Default: 10 min
Maximum: 4 days (96 hours)

Hardware Accelerated GUI¶

hwgui¶

Default: 10 min
Maximum: 4 days (96 hours)