table of contents
other versions
- jessie-backports 8.1.9+dfsg-1~bpo8+1
- stretch 8.1.9+dfsg-4+deb9u2
- testing 8.1.9+dfsg-9
- unstable 8.1.9+dfsg-9
SGE_PRIORITY(5) | Grid Engine File Formats | SGE_PRIORITY(5) |
NAME¶
sge_priority - Grid Engine job prioritiesDESCRIPTION¶
Grid Engine provides a means for controlling job dispatch and run-time priorities. The dispatch priority indicates the relative importance of pending jobs and determines the order in which Grid Engine initially considers dispatching jobs to queue instances, if the relevant resources are available. (The actual running order may be influenced may be influenced by other factors, such as reservations.) The run-time priority determines the CPU allocation that the operating system assigns to jobs.JOBS DISPATCH PRIORITY¶
A job's dispatch priority (display in the "reduced" output format of is affected by a number of factors:- •
- the identity of the submitting user;
- •
- the project under which the job is submitted (or alternatively, the default project of the submitting user);
- •
- any resources requested by the job;
- •
- the job's submit time;
- •
- the job's initiation deadline time (if specified);
- •
- the -p priority specified for the job (also known as the POSIX priority " pprio").
npprior = normalized(ppri) nurg = normalized(urg) ntckts = normalized(tckts) prio = weight_priority * npprio + weight_urgency * nurg + weight_ticket * ntcktsThe higher a job's priority value, the earlier it gets dispatched. The urgency policy defines an urgency value for each job. The urgency value
urg = rrcontr + wtcontr + dlcontr
rrcontr = Sum over all(hrr)
hrr = rurg * assumed_slot_allocation * request
hrr = rurg
wtcontr = waiting_time * weight_waiting_time
dlcontr = weight_deadline / free_time
tckts = ftckt + otckt + stckt The ticket policies provide a broad range of means for influencing both job dispatch and runtime priorities on a per job, per user, per project, and per department basis. The -ext option displays ticket information for jobs.
JOB RUN-TIME PRIORITY¶
The run-time priority can be dynamically adjusted in order to meet the goals set with the ticket policy when execution hosts are over-subscribed. Dynamic run-time priority adjustment can be turned on globally using reprioritize in and reprioritize_interval in If no dynamic run-time priority adjustment is done at a host level, the priority specification in is in effect. Note that urgency and POSIX priorities do not affect runtime priority.SEE ALSO¶
COPYRIGHT¶
See for a full statement of rights and permissions.2007-01-05 | SGE 8.1.3pre |