HP-UX Workload Manager User's Guide

Configuring WLM
Defining SLOs
Chapter 5198
When configuring WLM on a partition, be sure to select
a value for lower_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 The lower_bound_request value is not a hard limit:
Higher priority SLOs may consume all CPU resources
before all SLOs are granted CPU resources. However,
the associated workload group’s gmincpu value is a
hard limit. It serves as the group’s minimum CPU
allocation when it represents more CPU resources than
the mincpu values used in the group’s SLOs. The
gmincpu value is also used to determine the group’s
minimum CPU allocation in SLOs with cpushares
statements but no mincpu statements. For information
on the default gmincpu value, see the gmincpu section
“Specifying a group’s minimum CPU resources
(optional)” on page 175. Similarly, hmincpu is a hard
limit for allocation to a host.
upper_bound_request
Is an integer greater than or equal to
lower_bound_request. upper_bound_request is the
maximum number of CPU shares the SLO’s controller
can request.
upper_bound_request is out of the total CPU
resources, which is 100 multiplied by the number of
cores (if you set the tunable absolute_cpu_units to 1
or it is implied by other elements in your
configuration)—or just 100 by default.
If you specify an upper_bound_request greater than
the total CPU resources, WLM treats it as equal to the
total CPU resources.
To have a maximum request of 3 cores on an 8-core
system with absolute_cpu_units enabled
(absolute_cpu_units = 1), you would specify:
maxcpu = 300;