In O2 we minimized the number of available partitions (or queues) to simplify the job submission process.
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.
Note 2: all partitions can run single or multi-core jobs (O2 does not have an mcore queue). For more information about parallel jobs in O2 read our dedicated wiki page
Details about the available partitions are reported in the table below
|Job Type||Priority||Max cores||Max runtime limit||Min runtime limit|
2 job limit, 20 core limit, 250GB / job memory limit
|12||20||12 hours||n/a||20 core limit, 250GB / job memory limit|
|medium||6||20||5 days||12 hours||20 core limit, 250GB / job memory limit|
|long||4||20||30 days||5 days||20 core limit, 250GB / job memory limit|
|5 days||n/a||invite-only. Email rchelp|
limit 2 jobs running at once (like Orchestra priority queue), 20 core per job limit
250GB / job memory limit
limit of a 5 concurrently cores per user
for transfers between O2 and
See File Transfer for more information.
Invite-only. Email rchelp.
|gpu||n/a||20||120 GPU hours||n/a||see the Using O2 GPU resources page for more details|
|highmem||n/a||16||5 days||n/a||invite-only. Email rchelp|