Platform LSF Administration Guide Version 6.2

Chapter 17
Goal-Oriented SLA-Driven Scheduling
Administering Platform LSF
319
GOAL: VELOCITY 8
ACTIVE WINDOW: (9:00-17:30)
STATUS: Active:On time
SLA THROUGHPUT: 0.00 JOBS/CLEAN_PERIOD
GOAL: DEADLINE
ACTIVE WINDOW: (17:30-9:00)
STATUS: Inactive
SLA THROUGHPUT: 0.00 JOBS/CLEAN_PERIOD
NJOBS PEND RUN SSUSP USUSP FINISH
0 0 0 0 0 0
◆ The throughput goal of service class Inuvik is always active. bsla displays:
❖ Status as active and on time
❖ An optimum number of 5 running jobs to meet the goal
❖ Actual throughput of 10 jobs per hour based on the last CLEAN_PERIOD
% bsla Inuvik
SERVICE CLASS NAME: Inuvik
-- constant throughput
PRIORITY: 20
GOAL: THROUGHPUT 6
ACTIVE WINDOW: Always Open
STATUS: Active:On time
SLA THROUGHPUT: 10.00 JOBs/CLEAN_PERIOD
OPTIMUM NUMBER OF RUNNING JOBS: 5
NJOBS PEND RUN SSUSP USUSP FINISH
110 95 5 0 0 10
Tracking historical behavior of an SLA (bacct)
Use bacct to display historical performance of a service class. For example, service
classes
Inuvik and Tuktoyaktuk configure throughput goals.
% bsla
SERVICE CLASS NAME: Inuvik
-- throughput 6
PRIORITY: 20
GOAL: THROUGHPUT 6
ACTIVE WINDOW: Always Open
STATUS: Active:On time
SLA THROUGHPUT: 10.00 JOBs/CLEAN_PERIOD
OPTIMUM NUMBER OF RUNNING JOBS: 5
NJOBS PEND RUN SSUSP USUSP FINISH
111 94 5 0 0 12
--------------------------------------------------------------
SERVICE CLASS NAME: Tuktoyaktuk
-- throughput 3
PRIORITY: 15