User Tools

Site Tools


aurora_cluster:how_scheduling_works

This is an old revision of the document!


How Aurora scheduling works

In this section I try to explain how your job requests are treated on the hep partition.

anyway long story short: - if one submits to the project HEP 2016/1-4, it doesn't matter who you are, if you're member of the project your requests will be processed FIFO (first in, first out. The first to submit will be the first to have their jobs processed). All other project members running or queued in front of you will have higher priority –in other words, there is no priority or fair share among members of the same project. It's like if you were a single person submitting jobs. - if the cluster is busy, requesting an interactive session may take time and fail. The scheduler will happily allocate resources for you, but if you ask an interactive session with say 6 cores and there is no machine with 6 cores free, the scheduler cannot fullfill the request. If you submit a batch job, the scheduler will queue it for you with the LIFO strategy described above. So one suggestion from Lunarc is to put the long, slow jobs first and the fast short ones later, so you give others more and more space as you finish processing the slow ones. - Fairness is enforced among the three projects using the hep partition (HEP 2016/1-3, HEP 2016/1-4, HEP 2016/1-5) that means every project is allocated 1/3 of computing power per month. Once one project exceeds that 1/3, it will be harder for members of that project to get resources when the other projects are running, because there is a debt of computing power towards them. This happens only when the cluster is being used by all, which is quite rare. But if at some point each project is using a considerable amount of computing power, it is for sure that all project members will have to wait in the queue to be allocated. Remember that the allocation is what you ASK for in the sbatch script: once is allocated is yours and others cannot take it. -

aurora_cluster/how_scheduling_works.1551949250.txt.gz · Last modified: 2019/03/07 09:00 by florido

Accessibility Statement