HP-UX Workload Manager User's Guide

Configuring WLM
Defining the PRM components (optional)
Chapter 5 177
With extended_shares enabled in this scenario, the
minimum allocation value would be 6.4 or 7.2, which
are the two nearest multiples of .8.
For more information on absolute CPU units, see the
section “Using absolute CPU units” on page 217.
If the sum of all the gmincpu values is greater than the
system’s total CPU resources, the values are treated as
CPU resource requests that are to be met before any
other requests are considered. weight values do apply.
When configuring WLM on a partition, be sure to select
a value for min 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
(cores).
NOTE For information on the effect of this keyword in passive mode, see
“Passive mode versus actual WLM management” on page 238.
Specifying a group’s maximum CPU resources
(optional)
You can assign workload groups a maximum number of CPU shares.
This maximum is a hard upper limit; the group will never receive more
than this maximum, as opposed to the maxcpu value in slo structures,
which merely specifies the maximum CPU request the SLO controller
can make. (The OTHERS group may receive more than its maximum if
other groups have received their maximum CPU resources and there are
still CPU resources left.)
To specify the maximum number of CPU shares a group receives, use the
gmaxcpu keyword in the prm structure, according to the following syntax:
gmaxcpu = group : max [, ...];
where
group Is the workload group name.