HP-UX Workload Manager User's Guide

How WLM manages workloads
Shares-based SLOs vs goal-based SLOs
Chapter 3118
• With the WLM global arbiter configuration file activated using the
-l option to wlmpard, the global arbiter adds data to the
/var/opt/wlm/wlmpardstats/ statistics log file.
Shares-based SLOs vs goal-based SLOs
WLM supports two types of SLOs:
•Shares-based SLOs
A shares-based SLO allows you to specify either a fixed allocation of
shares or a shares-per-metric allocation for a workload. A
shares-per-metric allocation is of the form “x shares of the CPU
resources for each metric y”.
A shares-based SLO has a priority. It may also have maximum and
minimum CPU request bounds and an explicit shares request.
However, it does not have an explicit goal.
• Goal-based SLOs
A goal-based SLO has a specified performance or usage goal.
WLM automatically changes CPU allocations for an SLO’s associated
workload based on the:
— Performance or usage (utilization) of the workload in the group
—SLO’s priority
— Available resources
A workload’s performance is tracked by a data collector and reported
to WLM, as explained in the section “How WLM gets application
data” on page 119. For an SLO with a usage goal, WLM tracks the
data itself.
You can simultaneously use an SLO with a fixed shares allocation and
goal-based SLOs on the same workload.