From 75f120390858803e3cf46e1525c57ef179ad27e7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Roman=20Sl=C3=ADva?= <roman.sliva@vsb.cz>
Date: Wed, 28 Feb 2024 15:03:29 +0100
Subject: [PATCH] Update job-priority.md - Technical Details

---
 docs.it4i/general/job-priority.md | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/docs.it4i/general/job-priority.md b/docs.it4i/general/job-priority.md
index 7e2a0dbaf..3dfde3277 100644
--- a/docs.it4i/general/job-priority.md
+++ b/docs.it4i/general/job-priority.md
@@ -34,7 +34,7 @@ Job age has the least impact on execution priority. It is very, very difficult f
 
 ### Formula
 
-Job execution priority calculated as:
+Job execution priority is calculated as:
 
 ---8<--- "job_sort_formula.md"
 
@@ -55,6 +55,21 @@ Specifying more accurate timelimit enables better scheduling, better execution t
 
 ---8<--- "mathjax.md"
 
+## Technical Details
+
+Priorities are set using Slurm's [Multifactor Priority Plugin][1]. Current settings are as follows:
+
+```
+$ grep ^Priority /etc/slurm/slurm.conf
+PriorityFlags=DEPTH_OBLIVIOUS
+PriorityType=priority/multifactor
+PriorityDecayHalfLife=7-0
+PriorityMaxAge=14-0
+PriorityWeightAge=100000
+PriorityWeightFairshare=10000000
+PriorityWeightPartition=1000000000
+```
+
 ## Inspecting Job Priority
 
 One can inspect job priority using `sprio` command. Job priority is in the field PRIORITY and it is comprised of PARTITION, FAIRSHARE and AGE priorities.
@@ -65,5 +80,6 @@ $ sprio -l -j 894782
          894782 qgpu         user1  service  300026688          0         17          0      26671          0  300000000     normal          0           0
 ```
 
+[1]: https://slurm.schedmd.com/priority_multifactor.html
 
 [a]: https://extranet.it4i.cz/rsweb/karolina/queues
-- 
GitLab