HP-UX Workload Manager User's Guide

Configuring WLM
Defining SLOs
Chapter 5 205
If the workload group can get a larger allocation from
an SLO with an absolute allocation request at that
priority, it does so. This absolute request can come from
an SLO that uses cpushares with total or from an
SLO that uses only the mincpu and maxcpu keywords.
total Makes absolute allocation requests starting from 0.
The request is exactly equal to value, within the
bounds formed by the SLO’s mincpu and maxcpu
values, if specified.
If the associated workload group can get a larger
allocation of shares from SLOs of higher or equal
priority making absolute allocation requests, it does so.
For example, to have a fixed allocation of 300 CPU shares assigned to a
workload, specify cpushares as follows (this assumes absolute mode is
enabled, where 300 shares equals 3 cores):
cpushares = 300 total;
Specifying a shares-per-metric allocation request
(optional)
An SLO can directly express an allocation request using the cpushares
keyword. This keyword allows you to make allocation requests of the
form “x shares of the CPU resources for each metric y”. For example, you
could give an Oracle instance n CPU shares for each process in the
instance.
The cpushares syntax is:
cpushares = value { more | total } [ per metric met [ plus offset ] ];
For details on the syntax, see “Specifying a shares-per-metric allocation
request (optional)” on page 472.
Specifying when the SLO is active (optional)
Use the keywords condition and exception to indicate when the SLO
is active. The values of these keywords form Boolean expressions. The
SLO is active when the condition expression is true, and the exception
expression is false. By default, the expressions are set so that the SLO is
always active.
The condition and exception keywords are optional.