Platform LSF Reference Version 6.2

lsb.serviceclasses
Platform LSF Reference
459
Default
None
GOALS
Syntax
GOALS=[
throughput | velocity | deadline] [\
[
throughput | velocity | deadline] ...]
Description
Required. Defines the service-level goals for the service class. A service class can have
more than one goal, each active at different times of the day and days of the week.
Outside of the time window, the SLA is inactive and jobs are scheduled as if no service
class is defined. LSF does not enforce any service-level goal for an inactive SLA.
The time windows of multiple service-level goals can overlap. In this case, the largest
number of jobs is run.
An active SLA can have a status of
On time if it is meeting the goal, and a status
Delayed, if it is missing its goals.
A service-level goal defines:
◆ throughput—expressed as finished jobs per hour and an optional time window when
the goal is active. throughput has the form:
GOALS=[THROUGHPUT num_jobs timeWindow [(time_window)]]
If no time window is configured, THROUGHPUT can be the only goal in the
service class. The service class is always active, and
bsla displays
ACTIVE WINDOW: Always Open.
◆ velocity—expressed as concurrently running jobs and an optional time window when
the goal is active. velocity has the form:
GOALS=[VELOCITY num_jobs timeWindow [(time_window)]]
If no time window is configured, VELOCITY can be the only goal in the service
class. The service class is always active, and
bsla displays ACTIVE WINDOW:
Always Open
.
◆ deadline—indicates that all jobs in the service class should complete by the end of
the specified time window. The time window is required for a deadline goal. deadline
has the form:
GOALS=[DEADLINE timeWindow (time_window)]
Time window
format
The time window of an SLA goal has the standard form:
[day:]hour[:minute]
with the following ranges:
◆ day of the week: 0-6
◆ hour: 0-23
◆ minute: 0-59
Specify a time window one of the following ways:
◆ hour-hour
◆ hour:minute-hour:minute
◆ day:hour:minute-day:hour:minute