HP-UX Workload Manager User's Guide

Configuring WLM
Tuning the metrics and the SLOs
Chapter 5 223
attempted to place in the group with prmrun or prmmove are moved to the
group. (For information on how WLM determines which group
assignment takes precedence when the same process is identified by
multiple records, see “How the application manager affects workload
group assignments” on page 459.)
NOTE When WLM is managing PSETs, do not change PSET settings by using
the psrset command. Only use WLM to control PSETs.
Capturing your collectors’ stderr (optional)
Because they are started by a daemon process, data collectors do not
have a stderr on which to communicate errors. The coll_stderr tunable
allows you to capture these errors. Specify coll_stderr using the
following syntax:
coll_stderr = file;
For details on the syntax, see “Capturing your collectors’ stderr
(optional)” on page 479.
Smoothing metric values (optional)
Use the cntl_smooth keyword to get a running average of a metric from
a data collector, smoothing out dips and spikes in the metric before it is
used by WLM. Specify cntl_smooth using the following syntax:
cntl_smooth = smoothing_value;
For details on the syntax, see “Smoothing metric values (optional)” on
page 480.
Controlling averaging in usage controllers (optional)
Use the cntl_avg keyword to control averaging in usage controllers. By
default, averaging is enabled (cntl_avg=1). With averaging disabled
(cntl_avg=0), only the most recent interval’s usage data is used for a
usage metric.
This tunable is ignored for metrics that are not CPU usage metrics.