Queues

The different queues are organized to follow the different hardware and usages:

• large: This queue is a routing queue dispatching jobs in execution queue, large_ivy. It addresses jobs only to Ivy Bridge nodes and is dedicated to large massively parallel jobs. Following limits are applied to this queue:

  • Job placement on nodes is exclusive.
  • Minimum number of cpus per job = 96
  • Maximum number of cpus per job = 4320
  • Walltime maximum = 24 hours
• main: This is the default queue.

  • Following limits are applied to main queue:
    • Walltime maximum = 168 hours
    • Maximum number of cpus per job = 192
  • The main queue is a routing queue dispatching jobs in execution queues:
    • main_has: default execution queue. It addresses jobs only to fit or fat Haswell nodes (accounting based on fit nodes). Nothing to add.
      • Following limits are applied to this execution queue:
        • Maximum number of cpus per user = 480
        • Maximum number of cpus per project = 960
    • main_has_fat: It addresses jobs only to fat Haswell nodes (accounting based on fat nodes). To use this queue, add:
      #PBS -l model=haswell_fat
    • main_has_xfat: It addresses jobs only to xfat Haswell nodes (accounting based on xfat nodes). To use this queue, add:
      #PBS -l model=haswell_xfat
  • Do not submit jobs directly in the execution queues.
  • Job placement on nodes in queue main is shared.
• visu: This queue is a routing queue dispatching visualisation jobs on the 2 graphic nodes. Each visualisation session can required at maximum: 12 cores, 126000MB of memory and 1 GPU.

  • execution queues:
    • visu2: It addresses jobs to the available GPU of each virtual node
  • Do not submit jobs directly in the execution queues.
• Restricted access queues: zen, diags, or ded_ for dedicated time, ...
• Reservation can be done by the support on demand.

Check the queue properties and limits with the command:
qstat -Qf

The cstat command (non standard) displays nodes/queues jobs repartition.