Help:HPCC Torque Queues
Job Queues on the CSDMS HPCC
.jpg)
We have defined a set of queues that you can submit your jobs to on beach. Although you can submit your job to a queue directly, generally your job will be routed to an appropriate queue, given the resources you request. As such, it is important that you specify what resources you will need. Of particular importance in the amount of memory that your job will use and the amount of time you estimate your job will take to run.
Please note that some of these queues have maximum runtimes associated with them. This means that your job will be killed if it runs over the queue's time limit.
Cheat Sheet
Job queues that you can submit to directly,
| Queue | Max Run Time | Max Memory | Max Nodes | Description |
|---|---|---|---|---|
| debug | 2 hours | 16 GB | 54 | Short jobs that might be used for testing |
| vip | 1 day | 16 GB | 54 | Important jobs that need to get done now |
Queues that you job will be routed to based on resource needs that you specify,
| Queue | Max Run Time | Max Memory | Max Nodes | Description |
|---|---|---|---|---|
| default | 4 days | 16 GB | 54 | Jobs that should be done within a few days |
| long | unlimited | 16 GB | 54 | Jobs that will run for a long time |
| himem | unlimited | 32 GB | 8 | Jobs that need to use memory-rich nodes |
Queue Status
Use qstat to get an up-to-date summary of the queues.
> qstat -q
Queue Memory CPU Time Walltime Node Run Que Lm State
---------------- ------ -------- -------- ---- --- --- -- -----
debug -- 02:00:00 -- -- 2 0 -- E R
vip -- 24:00:00 -- -- 0 0 -- E R
ocean-owner -- -- -- -- 0 0 -- E R
route -- -- -- -- 0 0 -- E R
himem -- -- -- -- 7 0 -- E R
long 15gb -- -- -- 1 0 12 E R
default 15gb 96:00:00 96:00:00 -- 0 0 -- E R
total -- -- -- -- 0 0 -- E R
wrf -- -- -- -- 0 0 -- E R
ocean -- -- -- -- 0 0 -- E R
wrf-owner -- -- -- -- 0 0 -- E R
----- -----
10 0
