From 5ecf6bfe94ce79166e7f72f4ba9b65f757f0bd22 Mon Sep 17 00:00:00 2001 From: Brian Christiansen <brian@schedmd.com> Date: Mon, 31 Aug 2015 16:01:26 -0700 Subject: [PATCH] Update TRESBillingWeights docs. --- doc/html/priority_multifactor.shtml | 2 +- doc/man/man5/slurm.conf.5 | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/html/priority_multifactor.shtml b/doc/html/priority_multifactor.shtml index f5d621772c2..5dcf281e6df 100644 --- a/doc/html/priority_multifactor.shtml +++ b/doc/html/priority_multifactor.shtml @@ -166,7 +166,7 @@ computing resources described below.</P> <P> Slurm's fair-share factor is a floating point number between 0.0 and 1.0 that reflects the shares of a computing resource that a user has been allocated and the amount of computing resources the user's jobs have consumed. The higher the value, the higher is the placement in the queue of jobs waiting to be scheduled.</P> <P> By default, the computing resource is the computing cycles delivered by a -machine in the units of processor*seconds. Other resources can be taken into +machine in the units of allocated_cpus*seconds. Other resources can be taken into account by configuring a partition's TRESBillingWeights option. The TRESBillingWeights option allows you to account for consumed resources other than just CPUs by assigning different billing weights to different Trackable diff --git a/doc/man/man5/slurm.conf.5 b/doc/man/man5/slurm.conf.5 index d5c6dd447c0..b4331aff13e 100644 --- a/doc/man/man5/slurm.conf.5 +++ b/doc/man/man5/slurm.conf.5 @@ -4087,6 +4087,12 @@ will be MAX(1*1.0, 8*0.25) + (0*2.0) = 2.0. If TRESBillingWeights is not defined then the job is billed against the total number of allocated CPUs. + +\fBNOTE:\fR TRESBillingWeights is only used when calcuating fairshare and +doesn't affect job priority directly as it is currently not used for the size of +the job. If you want TRES' to play a role in the job's priority then refer to +the PriorityWeightTRES option. + .RE .TP -- GitLab