HP-UX Workload Manager User's Guide

Advanced WLM usage: Using performance metrics
Configuring WLM for metric-based SLOs
Appendix H 473
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).
request_value is bounded by the SLO’s mincpu and
maxcpu values, if specified.
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 request_value
(discussed in the cpushares keyword description),
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.
per metric Is an optional clause. Using per metric forms an
allocation request by multiplying value by the metric
met in request_value (discussed in the cpushares
keyword description).
met Is the text string naming the metric to be used. The
metric string must also be specified in a tune structure
that indicates the path to the data collector executable
providing the metric. met cannot contain the slash (/)
character, start with an underscore (_), or be more than
255 characters.
plus Is an optional clause, for use only with the per metric
clause, that allows you to increase or decrease the
number of CPU shares to be requested as part of the
request_value, which is discussed in the cpushares
keyword description.
offset Is a floating-point value (either positive or negative)
specifying the number of shares to use as an offset in
the request_value (discussed in the cpushares
keyword description).