QOS
You have to specify a Quality of Service (QOS) for each job submitted to Slurm. The QOSs are defined in the Slurm database.
The slurm configuration for resource sharing is not yet stabilized.
the glicid_qos command allows you to visualize the restrictions that are applied.
|
As said in the concepts, the chosen QoS will affect greatly the priority of your job in the queue.
At the time of writing, here are the available QoS on GLiCID. To have an up-to-date version, use the glicid_qos command.
Name |
Priority |
MaxWall |
Flags |
MaxJobsPU |
MaxJobsAccruePU |
MaxTRESPU |
normal |
1 |
00:05:00 |
DenyOnLimit |
1 |
0 |
cpu=12,gres/gpu=1 |
short |
50 |
1-00:00:00 |
DenyOnLimit |
10 |
10 |
cpu=512,gres/gpu=2 |
medium |
40 |
3-00:00:00 |
DenyOnLimit |
10 |
10 |
cpu=512,gres/gpu=2 |
long |
30 |
8-00:00:00 |
DenyOnLimit |
5 |
10 |
cpu=512,gres/gpu=2 |
unlimited |
10 |
DenyOnLimit |
1 |
cpu=1920 |
||
debug |
300 |
00:20:00 |
DenyOnLimit |
1 |
5 |
cpu=192,gres/gpu=2 |
priority |
200 |
8-00:00:00 |
DenyOnLimit |
288 |
10 |
|
quick |
100 |
03:00:00 |
DenyOnLimit |
50 |
10 |
cpu=512,gres/gpu=4 |
gpus |
70 |
03:00:00 |
DenyOnLimit |
1 |
10 |
|
verylong |
10 |
25-00:00:00 |
DenyOnLimit |
2 |
10 |
cpu=96 |
large |
40 |
2-00:00:00 |
DenyOnLimit |
400 |
10 |
cpu=400 |