Pegasus Job Queues

Pegasus queues are organized using limits like job size, job length, job purpose, and project. In general, users run jobs on Pegasus with equal resource shares. Current or recent resource usage lowers the priority applied when LSF assigns resources for new jobs from a user’s account.

Parallel jobs are more difficult to schedule as they are inherently larger. Serial jobs can “fit into” the gaps left by larger jobs if serial jobs use short enough run time limits and small enough numbers of processors.

The parallel queue is available for jobs requiring 16 or more cores. Submitting jobs to this queue *requires* resource distribution -R "span[ptile=16]".

The bigmem queue is available for jobs requiring nodes with expanded memory. Submitting jobs to this queue requires project membership. Do not submit jobs that can run on the general and parallel queues to the bigmem queue.

Warning

Jobs using less than 1.5G of memory per core on the bigmem queue are in violation of acceptable use policies and the IDSC account responsible for those jobs may be suspended (Policies).

Pegasus Job Queues
Queue Name Processors (Cores) Memory Wall time default / max Description
general 15- 24GB max 1 day / 7 days jobs up to 15 cores, up to 24GB memory
parallel 16+ 24GB max 1 day / 7 days parallel jobs requiring 16 or more cores, up to 24GB memory.
requires resource distribution -R “span[ptile=16]”
bigmem 64 max 250GB max 4 hours / 5 days jobs requiring nodes with expanded memory
debug 64 max 24GB max 30 mins / 30 mins job debugging
interactive 15- 250GB max 6 hours / 1 day interactive jobs
max 1 job per user
gpu xx 320 max 1 day / 7 days gpu debugging restricted queue
phi xx 320 max 1 day / 7 days phi debugging restricted queue