LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 463
Job Priorities
PRIORITY = 30
NICE = 20
FAIRSHARE = USER_SHARES [[user1, 5000] [user2, 5000] [others, 1]]
APS_PRIORITY = WEIGHT [[JPRIORITY, 1] [QPRIORITY, 10] [FS, 100]]
QUEUE_GROUP = short
DESCRIPTION = For normal low priority jobs, running only if hosts
are lightly loaded.
End Queue
The APS value is now calculated as
APS_PRIORITY = 1 * (1 * job_priority + 10 * queue_priority) + 100 * user_priority
Example 3 Extending example 2, you now to add swap space to the APS value calculation. The
APS configuration changes to:
APS_PRIORITY = WEIGHT [[JPRIORITY, 1] [QPRIORITY, 10] [FS, 100] [SWAP, -10]]
And the APS value is now calculated as
APS_PRIORITY = 1 * (1 * job_priority + 10 * queue_priority) + 100 * user_priority + 1 *
(-10 * SWAP)
View pending job order by the APS value
Run bjobs -aps to see APS information for pending jobs in the order of absolute
scheduling priority. The order that the pending jobs are displayed is the order in
which the jobs are considered for dispatch.
The APS value is calculated based on the current scheduling cycle, so jobs are not
guaranteed to be dispatched in this order.
Pending jobs are ordered by APS value. Jobs with system APS values are listed first,
from highest to lowest APS value. Jobs with calculated APS values are listed next
ordered from high to low value. Finally, jobs not in an APS queue are listed. Jobs
with equal APS values are listed in order of submission time.
If queues are configured with the same priority,
bjobs -aps may not show jobs in
the correct expected dispatch order. Jobs may be dispatched in the order the queues
are configured in
lsb.queues. You should avoid configuring queues with the same
priority.
Example bjobs -aps
output
The following example uses this configuration;
◆ The APS only considers the job priority and queue priority for jobs from
normal queue (priority 30) and short queue (priority 20)
❖ APS_PRIORITY = WEIGHT [[QPRIORITY, 10] [JPRIORITY, 1]]
❖ QUEUE_GROUP = short
◆ Priority queue (40) and idle queue (15) do not use APS to order jobs
◆ JOB_PRIORITY_OVER_TIME=5/10 in lsb.params
◆ MAX_USER_PRIORITY=100 in lsb.params
bjobs -aps was run at 14:41:
bjobs -aps
JOBID USER STAT QUEUE FROM_HOST JOB_NAME SUBMIT_TIME APS
15 User2 PEND priority HostB myjob Dec 21 14:30 -