The Padobran computer cluster contains two job queues. The difference between the queues is in the execution time of the jobs. Each queue has a minimum and maximum execution time. Computation time refers to the "walltime" parameter, and does not depend on the number of requested cores.
The job is terminated at the end of the requested or assigned time.
| Queue | Number of nodes | Number of cores per node | Working memory per node (GB) | Job execution time (h) | TMPDIR |
|---|---|---|---|---|---|
| cpu | 25 | 128 | 475 | 00:00:00 - 168:00:00 | /beegfs-fast/scratch |
| cpu_30 | 25 | 128 | 475 | 168:00:01 - 720:00:00 | /beegfs-fast/scratch |
Using queues
The system is set up so that above all queues there is a RouteQ routing queue that ensures that jobs without a defined queue fall into the right job queue, based on the required computation time. If jobs do not ask for compute time in the job description, they are automatically assigned 48 hours and sent to the cpu queue.
Users are advised to search for runtime in order to increase the efficiency of using the cluster, but also to spend as little time as possible in the waiting queue.
If a user submits a job that requests a queue but does not define a runtime, the job will be allocated the maximum time in that queue.
If the job requests a queue, but also a time that does not correspond to the queue limits, a message will be displayed on the screen:
qsub: Job violates queue and/or server resource limits