From c45e41cee2258766c7fbef522ec67327af6fa37d Mon Sep 17 00:00:00 2001 From: Don Lipari <lipari1@llnl.gov> Date: Mon, 9 Feb 2009 18:23:02 +0000 Subject: [PATCH] Cosmetic changes to job_priority.shtml --- doc/html/job_priority.shtml | 33 +++++++++++++++++++-------------- 1 file changed, 19 insertions(+), 14 deletions(-) diff --git a/doc/html/job_priority.shtml b/doc/html/job_priority.shtml index cdc3bceba28..2c18e60db60 100644 --- a/doc/html/job_priority.shtml +++ b/doc/html/job_priority.shtml @@ -21,15 +21,20 @@ <P> The Multi-factor job priority plugin provides a very versatile facility for ordering the queue of jobs waiting to be scheduled. There are five factors that influence job priority:</P> -<UL> -<LI> <B>Age</B> the length of time a job has been waiting in the queue, eligible to be scheduled -<LI> <B>Fair-share</B> the difference between the portion of the computing resource that has been promised and the amount of resources that have been consumed -<LI> <B>Job size</B> the number of nodes a job is allocated -<LI> <B>Partition</B> a factor associated with each node partition -<LI> <B>QOS</B> a factor associated with each Quality Of Service -</UL> - -<P> Additionally, a weight can be assigned to each of the above factors. This provides the ability to enact a policy that blends a combination of any of the above factors in any portion desired. For example, a site could configure fair-share to be the dominant factor (say 70%), set the job size and the aging factors to each contribute 15%, and set the partition and QOS influences to zero.</P> +<DL> +<DT> Age +<DD> the length of time a job has been waiting in the queue, eligible to be scheduled +<DT> Fair-share +<DD> the difference between the portion of the computing resource that has been promised and the amount of resources that has been consumed +<DT> Job size +<DD> the number of nodes a job is allocated +<DT> Partition +<DD> a factor associated with each node partition +<DT> QOS +<DD> a factor associated with each Quality Of Service +</DL> + +<P> Additionally, a weight can be assigned to each of the above factors. This provides the ability to enact a policy that blends a combination of any of the above factors in any portion desired. For example, a site could configure fair-share to be the dominant factor (say 70%), set the job size and the age factors to each contribute 15%, and set the partition and QOS influences to zero.</P> <!--------------------------------------------------------------------------> <a name=general> @@ -45,21 +50,21 @@ Job_priority = (QOS_weight) * (QOS_factor) </PRE> -<P> All of the factors in this formula are floating point numbers that range from 0.0 to 1.0. The weights are unsigned, 32 bit integers. Consequently, the job's priority is a floating point number that ranges between 0 and 4294967295.0. The higher the number, the higher the job will be positioned in the queue, and the sooner the job will be scheduled. A job's priority, and hence its order in the queue, will vary over time. For example, the longer a job sits in the queue, the higher its priority will grow when the age_weight is non-zero.</P> +<P> All of the factors in this formula are floating point numbers that range from 0.0 to 1.0. The weights are unsigned, 32 bit integers. Consequently, the job's priority is a floating point number that ranges between 0.0 and 4294967295.0. The higher the number, the higher the job will be positioned in the queue, and the sooner the job will be scheduled. A job's priority, and hence its order in the queue, will vary over time. For example, the longer a job sits in the queue, the higher its priority will grow when the age_weight is non-zero.</P> <!--------------------------------------------------------------------------> <a name=age> <h2>Age Factor</h2> -<P> The age factor represents the length of time a job has been sitting in the queue and eligible to run. A job that depends on another job to complete will not increment the age factor. Also, a job whose limits exceed the allowable limits in effect will similarly not increment the age factor.</P> +<P> The age factor represents the length of time a job has been sitting in the queue and eligible to run. In general, the longer a job waits in the queue, the larger its age factor grows. However, the age factor for a dependent job will not change while it waits for the job it depends on to complete. Also, the age factor of a queued job whose node or time limits exceed the cluster's current limits will not change.</P> -<P> At some configurable length of time (<i>PriorityMaxAge</i>), the aging factor will max out to 1.0.</P> +<P> At some configurable length of time (<i>PriorityMaxAge</i>), the age factor will max out to 1.0.</P> <!--------------------------------------------------------------------------> <a name=jobsize> <h2>Job Size Factor</h2> -<P> The job size factor represents the number of nodes the job has requested. This factor can be configured to favor larger jobs or smaller jobs based on the state of the <i>PriorityFavorSmall</i> boolean in the slurm configuration file. When <i>PriorityFavorSmall</i> is 0, the larger the job, the greater its job size factor will be. A job that requests all the nodes on the machine will get a job size factor of 1.0. When the <i>PriorityFavorSmall</i> Boolean is 1, the single node job will receive the 1.0 job size factor.</P> +<P> The job size factor correlates to the number of nodes the job has requested. This factor can be configured to favor larger jobs or smaller jobs based on the state of the <i>PriorityFavorSmall</i> boolean in the slurm configuration file. When <i>PriorityFavorSmall</i> is 0, the larger the job, the greater its job size factor will be. A job that requests all the nodes on the machine will get a job size factor of 1.0. When the <i>PriorityFavorSmall</i> Boolean is 1, the single node job will receive the 1.0 job size factor.</P> <!--------------------------------------------------------------------------> <a name=partition> @@ -78,7 +83,7 @@ Job_priority = <h2>Fair-share Factor</h2> <!--------------------------------------------------------------------------> -<p style="text-align:center;">Last modified 6 February 2009</p> +<p style="text-align:center;">Last modified 9 February 2009</p> <!--#include virtual="footer.txt"--> -- GitLab