Platform LSF Running Jobs Version 6.2

Viewing Information about SLAs and Service Classes
Running Jobs with Platform LSF
60
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
ACTIVE WINDOW: Always Open
STATUS: Active:On time
SLA THROUGHPUT: 10.00 JOBs/CLEAN_PERIOD
THROUGHPUT: 6
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
GOAL: THROUGHPUT
ACTIVE WINDOW: Always Open
STATUS: Active:On time
SLA THROUGHPUT: 4.00 JOBs/CLEAN_PERIOD
THROUGHPUT: 3
OPTIMUM NUMBER OF RUNNING JOBS: 4
NJOBS PEND RUN SSUSP USUSP FINISH
104 96 4 0 0 4
These two service classes have the following historical performance. For SLA Inuvik,
bacct shows a total throughput of 8.94 jobs per hour over a period of 20.58 hours:
% bacct -sla Inuvik
Accounting information about jobs that are:
- submitted by users user1,
- accounted on all projects.
- completed normally or exited
- executed on all hosts.
- submitted to all queues.
- accounted on service classes Inuvik,
------------------------------------------------------------------------------
SUMMARY: ( time unit: second )
Total number of done jobs: 183 Total number of exited jobs: 1
Total CPU time consumed: 40.0 Average CPU time consumed: 0.2
Maximum CPU time of a job: 0.3 Minimum CPU time of a job: 0.1
Total wait time in queues: 1947454.0
Average wait time in queue:10584.0