HP-UX Workload Manager User's Guide

How WLM manages workloads
How a workload is managed (controllers)
Chapter 3 121
seconds varies in the wrong direction. Similarly, for a goal to have
greater than 100 transactions/minute, a reported performance of 80
transactions/minute varies in the wrong direction.
Regardless of the direction of underperformance or overperformance,
WLM adjusts CPU allocations to more closely match the SLO’s goal.
In the case of an SLO violation, however, WLM also sets EMS
resources to alert persons monitoring the system. For more
information on EMS resources, see “What EMS resources are
available?” on page 354.
You can also track SLO violations using wlminfo.
How conflicting SLOs are resolved (arbiter)
When CPU resources are insufficient to satisfy all SLO controller
requests, WLM must decide how to distribute CPU resources among the
workloads. In these cases, the WLM arbiter considers each controller’s
prioritized requests for CPU resources and the associated workloads’
weights to decide the proper allocation of CPU resources.
For an illustration showing the arbiter, see Figure 3-1 on page 115.
For information on priorities and weights, see “Specifying the priority
(required)” on page 193 and “Weighting a group so it gets more CPU
resources (optional)” on page 178.