Skip Nav

Queue Summary

The available queues and their associated limits are the same on all of our HPC systems. The following table lists the queues in order of priority from highest to lowest. The Queue Name is the name of the queue as it appears on the systems. The Job Class is the class of jobs that may be run in that queue. Queues without a Job Class can run any class of jobs. Max Wall Time is the maximum lifetime for any job running in a queue, and Max Cores per Job is the maximum number of cores that may be allocated to any single job in a given queue.

Summary of Queues on Pershing
Priority Queue
Name
Job
Class
Max Wall
Clock Time
Max Cores
Per Job
Comments
Highest debug Debug 1 Hour 512 User diagnostic jobs
Down Arrow for decreasing priority transfer N/A 24 Hours 1 Data transfer for user jobs
urgent Urgent 96 Hours N/A Designated urgent jobs by DoD HPCMP
staff N/A 368 Hours N/A ARL DSRC staff testing only. System testing and user support.
high High 96 Hours N/A Designated high-priority jobs by DoD HPCMP
challenge Challenge 168 Hours N/A Challenge projects only
cots Standard 96 Hours N/A Abaqus, Fluent, and Cobalt jobs
interactive Standard 12 Hours N/A Interactive jobs
standard-long Standard 200 Hours N/A ARL DSRC permission required
standard Standard 168 Hours N/A Non-Challenge user jobs
Lowest background Background 24 Hours N/A User jobs that will not be charged against the project allocation.