...
You can use the flow chart below to find out which partition is best for the type of jobs you plan to run.
...
Note 1: all partitions can currently be used to request interactive sessions; the interactive partition has a dedicated set of nodes and higher priority.
...
Details about the available partitions are reported in the table below
Partition | Job Type | Priority | Max cores per job | Max runtime limit | Min runtime limit | Notes |
---|---|---|---|---|---|---|
interactive | interactive | 14 | 20 | 12 hours | n/a | 2 job limit, 20 core/job limit, 250GiB / job memory limit |
short | batch & interactive | 12 | 20 | 12 hours | n/a | 20 core/job limit, 250GiB / job memory limit |
medium | 6 | 20 | 5 days | 12 hours | 20 core/job limit, 250GiB / job memory limit | |
long | 4 | 20 | 30 days | 5 days | 20 core/job limit, 250GiB / job memory limit | |
mpi | 12 | 640 | 5 days | n/a | invite-only. Email rchelp | |
priority | 14 | 20 | 30 days | n/a | limit 2 jobs running at once (like Orchestra priority queue), 20 core per job limit 250GiB / job memory limit | |
transfer | n/a | 4 | 5 days | n/a | limit of a 5 concurrently cores per user for transfers between O2 and See File Transfer for more information. Invite-only. Email rchelp. | |
gpu, gpu_quad | n/a | 20 | 5 days | n/a | additional limits apply to the GPU partition, see the Using O2 GPU resources page for more details | |
gpu_mpi_quad | n/a | 240 | 5 days | n/a | invite-only. Email rchelp | |
gpu_requeue | n/a | 20 | 24 hours | n/a | see O2 GPU Re-Queue Partition for additional details | |
highmem | n/a | 16 | 5 days | n/a | invite-only. Email rchelp |