From 8bd061d4d9cf2247fd4c0f4358d003f72e084e10 Mon Sep 17 00:00:00 2001 From: Roman Sliva <roman.sliva@vsb.cz> Date: Wed, 28 Feb 2024 11:23:00 +0100 Subject: [PATCH] Update job-priority.md --- docs.it4i/general/job-priority.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/docs.it4i/general/job-priority.md b/docs.it4i/general/job-priority.md index 4eadf01a6..3e2d0465c 100644 --- a/docs.it4i/general/job-priority.md +++ b/docs.it4i/general/job-priority.md @@ -8,7 +8,7 @@ Job execution priority is determined by these job properties (in order of import 1. queue priority 1. fair-share priority -1. eligible time +1. job age/eligible time ### Queue Priority @@ -24,15 +24,13 @@ Fair-share priority is calculated based on recent usage of resources. Fair-share Fair-share priority is used for ranking jobs with equal queue priority. -Usage decays, halving at intervals of 7 days (one week). +Usage decays, halving at intervals of 7 days. -### Eligible Time +### Job Age/Eligible Time -Eligible time is the amount of eligible time a job accrues while waiting to run. Jobs with higher eligible time gain higher priority. +The job age factor represents the length of time a job has been sitting in the queue and eligible to run. -Eligible time has the least impact on execution priority. Eligible time is used for sorting jobs with equal queue priority and fair-share priority. It is very, very difficult for eligible time to compete with fair-share priority. - -Eligible time can be seen in the `eligible_time` attribute of a job. +Job age has the least impact on execution priority. It is very, very difficult for eligible time to compete with fair-share priority. ### Formula -- GitLab