HP-UX Workload Manager User's Guide

Configuring WLM
Tuning the metrics and the SLOs
Chapter 5 221
tune {
transient_groups = 1;
}
NOTE Setting transient_groups equal to 1 in a configuration that does not
have a prm structure results in an invalid configuration.
With the transient_groups keyword set to 1: FSS groups with no active
SLOs are deleted and therefore use no resources; the minimum CPU
allocation for PSET groups becomes 0 (or the minimum specified by
gmincpu, if resources are available). However, groups associated with a
process map remain active and continue to receive the minimum
allocation of resources even if they have no active SLOs.
Using the transient_groups keyword does not throttle the resource
usage of processes in transient groups that are inactive. In fact, those
processes are moved—possibly to groups where they get more resources,
as discussed in the “Placement of processes” sections that follow.
The OTHERS group is never removed, regardless of its number of active
SLOs.
If an FSS workload group has been temporarily removed, its gmincpu
and gminmem values (if any) are ignored.
To prevent groups from being removed when they become inactive, while
providing them smaller minimum allocations, enable the
extended_shares tunable instead of the transient_groups tunable.
For information on the extended_shares tunable, see “Refining
granularity of CPU (and memory) allocation by increasing shares per
core (optional)” on page 219.
NOTE Do not create a condition statement that attempts to detect processes
in a transient group using tools such as glance or ps. Whenever the
group is deleted (FSS group) or assigned zero CPU resources
(PSET-based group), it is impossible for the system to place processes in
the group. The condition will then never detect the processes it is looking
for.