(Click to open topic with navigation)
Each component or subcomponent may be used to accomplish different objectives. WALLTIME can be used to favor (or disfavor) jobs based on their duration. Likewise, ACCOUNT can be used to favor jobs associated with a particular project while QUEUETIME can be used to favor those jobs waiting the longest.
Each priority factor group may contain one or more subfactors. For example, the Resource factor consists of Node, Processor, Memory, Swap, Disk, and PE components. From the table in Job Priority Factors section, it is apparent that the prioritization problem is fairly complex since every site needs to prioritize a bit differently. When calculating a priority, the various priority factors are summed and then bounded between 0 and MAX_PRIO_VAL, which is currently defined as 100000000 (one billion).
The mdiag -p command assists with visualizing the priority distribution resulting from the current job priority configuration. Also, the showstats -f command helps indicate the impact of the current priority settings on scheduler service distributions.