1SGE_PRIORITY(5) Grid Engine File Formats SGE_PRIORITY(5)
2
6 sge_priority - Grid Engine job priorities
7
9 Grid Engine provide means for controlling job dispatch and run-time
10 priorities. The dispatch priority indicates the importance of pending
11 jobs compared with each other and determines the order in which Grid
12 Engine dispatches jobs to queue instances. The run-time priority deter‐
13 mines the CPU allocation that the operating system assigns to jobs.
14 JOBS DISPATCH PRIORITY
16 A job's dispatch priority is affected by a number of factors:
17 · the identity of the submitting user
19 · the project under which the job is submitted (or alternatively, the
21 default project of the submitting user)
22 · any resources requested by the job
24 · the job's submit time
26 · the job's initiation deadline time (if specified)
28 · the -p priority specified for the job (also known as the POSIX pri‐
30 ority "pprio")
31 The effect of each of these is governed by the overall policy setup,
33 which is split into three top-level contributions. Each of these is
34 configured through the sched_conf(5) parameters weight_priority,
35 weight_ticket and weight_urgency. These three parameters control to
36 what degree POSIX priority, ticket policy, and urgency policy are in
37 effect. To facilitate interpretation, the raw priorities
38 ("tckts"/"urg"/"ppri") are normalized ("ntckts"/"nurg"/"npprior")
39 before they are used to calculate job priorities ("prio"). Normaliza‐
40 tion maps each raw urgency/ticket/priority value into a range between
41 0 and 1.
42 npprior = normalized(ppri)
44 nurg = normalized(urg)
45 ntckts = normalized(tckts)
46 prio = weight_priority * pprio +
48 weight_urgency * nurg +
49 weight_ticket * ntckts
50 The higher a job's priority value, the earlier it gets dispatched.
52 The urgency policy defines an urgency value for each job. The urgency
54 value
55 urg = rrcontr + wtcontr + dlcontr
57 consists of the resource requirement contribution ("rrcontr"), the
59 waiting time contribution ("wtcontr") and the deadline contribution
60 ("dlcontr").
61 The resource requirement contribution is adding up all resource
63 requirements of a job into a single numeric value.
64 rrcontr = Sum over all(hrr)
66 with an "hrr" for each hard resource request. Depending on the
68 resource type two different methods are used to determine the value to
69 be used for "hrr" here. For numeric type resource requests, the "hrr"
70 represents how much of a resource a job requests (on a per-slot basis
71 for pe jobs) and how "important" this resource is considered in compar‐
72 ison to other resources. This is expressed by the formula:
73 hrr = rurg * assumed_slot_allocation * request
75 where the resource's urgency value ("rurg") is as specified under
77 urgency in complex(5), the job's assumed_slot_allocation represents the
78 number of slots supposedly assigned to the job, and the per-slot
79 request is that which was specified using the -l qsub(1) option. For
80 string type requests the formula is simply
81 hrr = "rurg"
83 and directly assigns the resource urgency value as specified under
85 urgency in complex(5).
86 The waiting time contribution represents a weighted weighting time of
88 the jobs
89 wtcontr = waiting_time * weight_waiting_time
91 with the waiting time in seconds and the weight_waiting_time value as
93 specified in sched_conf(5).
94 The deadline contribution has an increasing effect as jobs approach
96 their deadline initiation time (see the -dl option in qsub(1)). It is
97 defined as the quotient of the weight_deadline value from sched_conf(5)
98 and the (steadily decreasing) free time in seconds until deadline ini‐
99 tiation time
100 dlcontr = weight_deadline / free_time
102 or is set to 0 for non-deadline jobs. After the deadline passes, the
104 value is static and equal to weight_deadline.
105 The ticket policy unites functional, override and share tree policies
107 in the ticket value ("tckts"), as is defined as the sum of the specific
108 ticket values ("ftckt"/"otckt"/"stckt") for each sub-policy (func‐
109 tional, override, share):
110 tckts = ftckt + otckt + stckt
112 The ticket policies provide a broad range of means for influencing both
114 job dispatch and runtime priorities on a per job, per user, per
115 project, and per department basis. See the Grid Engine Installation and
116 Administration Guide for details.
117 JOB RUN-TIME PRIORITY
119 The run-time priority can be dynamically adjusted in order to meet the
120 goals set with the ticket policy. Dynamic run-time priority adjustment
121 can be turned off (default) globally using reprioritize_interval in
122 sched_conf(5) If no dynamic run-time priority adjustment is done at a
123 host level, the priority specification in queue_conf(5) is in effect.
124 Note that urgency and POSIX priorities do NOT affect runtime priority.
126
128 sge_intro(1), complex(5), qstat(1), qsub(1), sched_conf(5), sge_conf(5)
129 Grid Engine Installation and Administration Guide
130
132 See sge_intro(1) for a full statement of rights and permissions.
133GE 6.1 $Date: 2007/01/05 19:56:10 $ SGE_PRIORITY(5)