HP-UX Workload Manager A.03.02.xx Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3

HP-UX Workload Manager Release Notes

New in this version

• CPU shares-per-metric allocations, which allow you to give a workload, for example, 2% of

the CPU resources for each process in the workload

• Multiple SLOs at different priorities, allowing you to have a “must meet” goal and

optional stretch goals for each workload

• Passive mode for analyzing a configuration’s behavior

• Audit and billing data

• Ability to set minimum and maximum amounts of cores available to a workload

• Time-based and metric-based activation of SLOs, including the ability to activate SLOs

associated with a Serviceguard package on failover

• GUI for creating, modifying, and deploying WLM configurations locally and on remote

systems

• Integration with HP Systems Insight Manager, allowing you to remotely control WLM

running on numerous nodes from a single point of administration

New in this version

This section lists the new or changed functionality for WLM A.03.02 and WLM A.03.02.02.

WLM A.03.02 supports HP-UX 11i v1 (B.11.11) and HP-UX 11i v2 (B.11.23). WLM A.03.02.02

supports HP-UX 11i v3 (B.11.31).

This document refers to both versions of WLM collectively as A.03.02.xx.

• WLM A.03.02.02 supports HP-UX 11i v3 (B.11.31).

• WLM A.03.02.02 supports the logical CPU (Hyper-Threading) feature, which is available

starting with HP-UX 11i v3 (B.11.31) for processors designed to support the feature and

that have the appropriate firmware installed. A logical CPU is an execution thread

contained within a core. Each core with Hyper-Threading enabled can contain multiple

logical CPUs. WLM supports the Hyper-Threading feature for PSET-based groups. WLM

automatically sets the Hyper-Threading state for the default PSET to optimize

performance. (The default PSET, also known as PSET 0, is where all FSS groups reside.)

When new PSETs are created, they inherit the Hyper-Threading state that the system

had before WLM was activated (inheritance is based on the system state prior to WLM

activation because WLM may change the Hyper-Threading setting for the default PSET to

optimize performance). Cores can be moved from one partition to another and will take on

the Hyper-Threading state of their destination PSET. You can override the default