... | ... | @@ -22,8 +22,8 @@ Backfilling is activated on Pyrene to maximize the cluster utilization and throu |
|
|
|
|
|
Backfilling allows a job of lower priority to run ahead of a pending job of higher priority, as long as the job of higher priority is not delayed as a result.
|
|
|
|
|
|
For instance, a job of higher priority requires 10 cores whereas only 5 are available in the cluster. Then, a job of lower priority can be launched if it requires no more than 5 cores, and if it ends before 10 cores become available for the job of higher priority.
|
|
|
For instance, a job of high priority requires 10 cores whereas only 5 are available in the cluster. Then, a job of low priority can be launched if it requires no more than 5 cores, and if it ends before 10 cores become available for the job of high priority.
|
|
|
|
|
|
Then, a good estimation of the walltime helps jobs to be run at the soonest possible date:
|
|
|
* Slurm needs this information to activate the backfilling.
|
|
|
* The more the specified job walltime is short, the more the job will be able to benefit from backfilling. |
|
|
\ No newline at end of file |
|
|
* The more its specified walltime is short, the more a job will be able to benefit from backfilling. |
|
|
\ No newline at end of file |