HP-UX Workload Manager User's Guide

Configuring WLM
Defining SLOs
Chapter 5 199
When configuring WLM on a partition, be sure to select
a value for upper_bound_request that makes sense in
terms of the limits placed on the partition when it was
created—namely its minimum and maximum number
of CPU resources.
NOTE An upper_bound_request may be ignored if the
associated workload’s CPU resources are already
limited by the group’s gmaxcpu value. In the case of
SLOs with cpushares statements but no maxcpu
statements, the group’s gmaxcpu value is still used to
limit CPU allocation. For information on the default
value of gmaxcpu, see the gmaxcpu section “Specifying a
group’s maximum memory (optional)” on page 184.
Similarly, hmaxcpu can limit CPU allocation to a host.
If lower_bound_request and upper_bound_request are equal, WLM
attempts to grant that exact amount of CPU resources; consequently,
specifying a goal would not be particularly useful because WLM would
not change the SLO’s CPU allocation to better achieve a goal.
For more information on absolute CPU units, see the section “Using
absolute CPU units” on page 217.
Specifying a goal (optional)
An SLO’s goal specifies either:
• A range for a workload’s CPU utilization
• Whether the workload’s performance should be less than or greater
than some specified floating-point value
Use the goal keyword to specify such goals.
The goal keyword is optional. If neither the goal nor cpushares
keyword is specified, the SLO is allocated CPU resources according to its
mincpu setting. For information on setting mincpu, see “Specifying the
lower and upper bound requests on CPU resources (optional)” on
page 196.