HP-UX Workload Manager User's Guide

Advanced WLM usage: Using performance metrics
Configuring WLM for metric-based SLOs
Appendix H472
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 ] ];
where
cpushares Is an optional keyword for making CPU allocation
requests. Using the variables in the syntax statement
shown previously, a request—which we will call
request_value—equates to one of the following forms:
value
value * met
value * met + offset
A request is additive when using the more keyword and
absolute when using the total keyword.
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.
value Specifies the number of CPU shares to request for the
associated workload group. This value is either an
integer or a floating-point number, not expressed in
exponential notation.
more Makes additive allocation requests by adding the
request_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