SGE_PRIORITY(5)            Grid Engine File Formats            SGE_PRIORITY(5)



NNAAMMEE
       sge_priority - Grid Engine job priorities

DDEESSCCRRIIPPTTIIOONN
       Grid  Engine  provide  means  for controlling job dispatch and run-time
       priorities. The dispatch priority indicates the importance  of  pending
       jobs  compared  with  each other and determines the order in which Grid
       Engine dispatches jobs to queue instances. The run-time priority deter-
       mines the CPU allocation that the operating system assigns to jobs.

   JJOOBBSS DDIISSPPAATTCCHH PPRRIIOORRIITTYY
       A job's dispatch priority is affected by a number of factors:

       +o  the identity of the submitting user

       +o  the  project under which the job is submitted (or alternatively, the
          default project of the submitting user)

       +o  any resources requested by the job

       +o  the job's submit time

       +o  the job's initiation deadline time (if specified)

       +o  the -p priority specified for the job (also known as the POSIX  pri-
          ority "pprio")

       The  effect  of  each of these is governed by the overall policy setup,
       which is split into three top-level contributions.  Each  of  these  is
       configured   through   the  _s_c_h_e_d___c_o_n_f(5)  parameters  wweeiigghhtt__pprriioorriittyy,
       wweeiigghhtt__ttiicckkeett and wweeiigghhtt__uurrggeennccyy.  These three  parameters  control  to
       what  degree  POSIX  priority, ticket policy, and urgency policy are in
       effect.   To   facilitate   interpretation,    the    raw    priorities
       ("tckts"/"urg"/"ppri")   are   normalized   ("ntckts"/"nurg"/"npprior")
       before they are used to calculate job priorities ("prio").   Normaliza-
       tion  maps each raw urgency/ticket/priority  value into a range between
       0 and 1.

          npprior = normalized(ppri)
          nurg    = normalized(urg)
          ntckts  = normalized(tckts)

          prio    = weight_priority * pprio +
                    weight_urgency  * nurg +
                    weight_ticket   * ntckts

       The 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

       consists  of  the  resource  requirement  contribution ("rrcontr"), the
       waiting time contribution ("wtcontr")  and  the  deadline  contribution
       ("dlcontr").

       The  resource  requirement  contribution  is  adding  up  all  resource
       requirements of a job into a single numeric value.

          rrcontr = Sum over all(hrr)

       with an "hrr"  for  each  hard  resource  request.   Depending  on  the
       resource  type two different methods are used to determine the value to
       be used for "hrr" here. For numeric type resource  requests  the  "hrr"
       represents  how  much of a resource a job requests (on a per-slot basis
       for pe jobs) and how "important" this resource is considered in compar-
       ison to other resources. This is expressed by the formula:

          hrr      = rurg * assumed_slot_allocation * request

       with the resources urgency value ("rurg") as specified under uurrggeennccyy in
       _c_o_m_p_l_e_x(5), the job's assumed_slot_allocation representing  the  number
       of  slots  supposedly  assigned  to the job and the per slot request as
       specified using the -l _q_s_u_b(1) option. For  string  type  requests  the
       formula is simply

          hrr      = "rurg"

       and  directly  assigns  the  resource  urgency value as specified under
       uurrggeennccyy in _c_o_m_p_l_e_x(5).

       The waiting time contribution represents a weighted weighting  time  of
       the jobs

          wtcontr = waiting_time * weight_waiting_time

       with  the  waiting time in seconds and the wweeiigghhtt__wwaaiittiinngg__ttiimmee value as
       specified in _s_c_h_e_d___c_o_n_f(5).

       The deadline contribution has an increasing  effect  as  jobs  approach
       their  deadline initiation time (see the -dl option in _q_s_u_b(1)).  It is
       defined as the quotient of the wweeiigghhtt__ddeeaaddlliinnee value from _s_c_h_e_d___c_o_n_f(5)
       and  the (steadily decreasing) free time in seconds until deadline ini-
       tiation time

          dlcontr = weight_deadline / free_time

       or is set to 0 for non-deadline jobs.  After the deadline  passes,  the
       value is static and equal to weight_deadline.

       The  ticket  policy unites functional, override and share tree policies
       in the ticket value ("tckts"), as is defined as the sum of the specific
       ticket  values  ("ftckt"/"otckt"/"stckt")  for  each  sub-policy (func-
       tional, override, share):

           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. See the Grid Engine Installation and
       Administration Guide for details.

   JJOOBB RRUUNN--TTIIMMEE PPRRIIOORRIITTYY
       The  run-time priority can be dynamically adjusted in order to meet the
       goals set with the ticket policy. Dynamic run-time priority  adjustment
       can  be  turned  off  (default) globally using rreepprriioorriittiizzee__iinntteerrvvaall in
       _s_c_h_e_d___c_o_n_f(5) If no dynamic run-time priority adjustment is done  at  a
       host level, the pprriioorriittyy specification in _q_u_e_u_e___c_o_n_f(5) is in effect.

       Note  that urgency and POSIX priorities do NNOOTT affect runtime priority.


SSEEEE AALLSSOO
       _s_g_e___i_n_t_r_o(1), _c_o_m_p_l_e_x(5), _q_s_t_a_t(1), _q_s_u_b(1), _s_c_h_e_d___c_o_n_f(5), _s_g_e___c_o_n_f(5)
       _G_r_i_d _E_n_g_i_n_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e

CCOOPPYYRRIIGGHHTT
       See _s_g_e___i_n_t_r_o(1) for a full statement of rights and permissions.



GE 6.0                   $Date: 2005/11/23 21:49:49 $          SGE_PRIORITY(5)
