HP-UX Workload Manager User's Guide

Configuring WLM
Defining SLOs
Chapter 5204
Specifying a fixed or additive allocation of CPU
shares (optional)
An SLO can directly express an allocation request using the cpushares
keyword. This keyword allows you to make fixed or additive allocation
requests, where a fixed allocation is a specific number of CPU shares,
while an additive allocation provides shares that are added to the
allocation from SLOs of higher or equal priority. (The cpushares
keyword also enables you to specify allocation requests of the form “x
shares of the CPU resources for each metric y”, as discussed in the next
section.)
The cpushares syntax for defining a fixed or additive allocation is:
cpushares = value { more | total };
where
value Is the number of CPU shares allocated for the
associated workload group. This value is either an
integer or a floating-point number, not expressed in
exponential notation.
A request is additive when using the more keyword and
absolute when using the total keyword. You must
specify either more or total.
You cannot specify both a goal statement and a
cpushares statement in the same SLO. Similarly, you
cannot have a workload group with one SLO that has a
goal statement and another SLO that has a
cpushares statement that includes more.
When you specify the cpushares keyword, the mincpu
and maxcpu keywords are optional.
more Makes additive allocation requests by adding the
value to other additive requests at the same priority
and to any requests from higher priority SLOs. If there
are no higher priority SLOs, the request is added to the
workload group’s gmincpu value, which is 1% of the
system’s total CPU resources by default (if the tunable
extended_shares is set to 1, the gmincpu value is 0.2%
by default).
value is bounded by the SLO’s mincpu and maxcpu
values, if specified.