HP-UX Workload Manager User's Guide

Configuring WLM
Tuning the metrics and the SLOs
Chapter 5220
extended_shares enabled, WLM can support 256 groups starting with
HP-UX 11i V2 Update 2 (the 64-group limit is still in effect on HP-UX 11i
V1).
The default value for extended_shares is 0, where 1 core consists of 100
shares.
Enable extended_shares if:
• You want finer granularity of allocation to FSS groups. This might be
preferred when the number of FSS groups or CPU resources is large.
• You want to use more than 63 FSS workload groups.
Enable extended_shares instead of transient_groups if you want to
prevent groups from being removed when they become inactive, while
providing smaller minimum allocations to these groups.
NOTE Regardless of the value of extended_shares, all configuration file values
and all values output by wlminfo are based on hundredths (when using
absolute CPU units). Enabling extended_shares affects the granularity
for all allocations and makes possible smaller minimum allocations.
Temporarily removing groups with inactive SLOs
(optional)
By default, all workload groups are always present—even those with no
active SLOs. A workload group with no active SLOs still requires 1% of
the total CPU resources for FSS groups (if extended_shares is set to 1,
an FSS group requires 0.2%) or a whole core for PSET-based groups,
unless it has a gmincpu value requesting more. If the group has a
gmincpu value requesting more, the group receives an allocation equal to
that value, if such resources are available. Similarly, if you are using
WLM memory management, the workload group with no active SLOs
receives 1% of the memory (if extended_shares is set to 1, it receives
0.2% of the memory, with incremental allocations of 0.1%), unless the
workload group has a gminmem value requesting more.
If you would prefer these groups to go away temporarily (as long as they
have no active SLOs) and consume no CPU or memory resources, set the
transient_groups tunable to 1 in a global tune structure: