Child pages
  • VK12) Available Queues and their limits
Skip to end of metadata
Go to start of metadata

LAST UPDATE 4th September 2019

Below is a table describing each of the partitions available on Viking.  These may change as we come to understand the workloads running on Viking and update these queues to reflect that. 

Queue nameMax timeMax jobs (running)Max CoresDefault mem per CPUMax memoryDefault timeNodes in PartitionComment
Nodes48 hrs100010004.8 GB4.8 TB8 hrs170Default partition for everything.
Test30 mins

2 (4 jobs can be queued)

81 GB16 GB10 mins170Partition for testing that jobs will start, need to request using –partition=test in job script.
himem48 hrsNo limit9611.875 GBN/A8 hrs3Partition for running jobs that require memory greater than that available in other partitions. Need to request using –partition=himem in job script.
Two nodes have 64 cores, one node has 96 cores.
GPU48 hrsNo limit809.6 GBN/A8 hrs2

Partition for running jobs that require GPUs, see documentation for details about how to request GPUs.
There are 4 GPUs and 40 cores on each GPU node.

Week7 daysNo limit4004 GBN/A48 hrs10Partition for jobs that need to run for longer than the 48h max time allowed by the nodes partition, but for less than a week. Need to request using –partition=week in job script
Month30 daysNo limit1204 GBN/A7 days3

Partition for jobs that need to run for longer than the 7 day max time allowed by the week partition, but for less than 30 days. Need to request using –partition=month in job script

  • No labels