HP-UX Workload Manager A.03.00 Release Notes for HP-UX 11i v1 and HP-UX 11i v2
HP-UX Workload Manager Release Notes
Known problems and workarounds
12
Capping issue
Issue WLM maintains CPU allocations for workloads by capping their CPU
access. Unfortunately, an algorithm in the CPU scheduler that WLM uses
does not always preserve capping.
You may see symptoms of this issue in wlminfo output. A portion of sample
output is shown below:
# wlminfo group
Workload Group PRMID CPU Shares CPU Util Mem Shares State
OTHERS 1 450.00 4.49 0.00 ON
g_nice 2 108.00 55.57 0.00 ON
g_nightly 3 0.00 0.00 0.00 OFF
g_team 4 6.00 0.00 0.00 ON
For a given group, if its “CPU Util” value is ever significantly greater than
its “CPU Shares” value, your system is affected by this issue. (“CPU Util”
values slightly above “CPU Shares” are normal.)
Workaround On HP-UX 11i v1 (B.11.11), install patches PHKL_30034, PHKL_30035,
PHKL_31993, PHKL_31995, and PHKL_32061. Install all these patches at
the same time.
On HP-UX 11i v2 (B.11.23), install the BUNDLE11i patch bundle. Any
version of this bundle is acceptable.
WLM uses only the assigned CPUs even with utilitypri set
Issue
In an Instant Capacity environment, with utilitypri set in your WLM
global arbiter configuration, WLM ensures all your owned CPUs are active.
However, if Instant Capacity is not in the environment, WLM uses only the
CPUs that were assigned to virtual partitions when the WLM global arbiter
(wlmpard) was started.
Workaround
Be sure to assign all the owned CPUs using vparmodify before you start
wlmpard. If wlmpard is already running, stop it (with the -k option) and
assign all the owned CPUs using vparmodify.