Job Submission partitions on Sapelo2

Batch partitions (queues) defined on the Sapelo2

There are different partitions defined on Sapelo2. The Slurm queueing system refers to queues as partition. Users are required to specify, in the job submission script or as job submission command line arguments, the partition and the resources needed by the job in order for it to be assigned to compute node(s) that have enough available resources (such as number of cores, amount of memory, GPU cards, etc). Please note, Slurm will not allow a job to be submitted if there are no resources matching your request. Please refer to Migrating from Torque to Slurm for more info about Slurm queueing system.

The following partitions are defined on the Sapelo2 cluster:

Partition Name	Time limit	Max jobs	Notes
batch	7 days		Regular nodes.
batch-30d	30 days	2	Regular nodes. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.
highmem_p	7 days		For high memory jobs
highmem_30d_p	30 days	2	For high memory jobs. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.
gpu_p	7 days		For GPU-enabled jobs.
gpu_30d_p	30 days	2	For GPU-enabled jobs. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.
inter_p	2 days		Regular nodes, for interactive jobs.
name_p	variable		Partitions that target different groups' buy-in nodes. The name string is specific to each group.