HP-UX Workload Manager User's Guide

Introduction
Examples of solutions that WLM provides
Chapter 1 55
When the Development workload is busy, the following priority 1 SLO
ensures that the workload gets 30% of the server’s CPU resources (the 30
shares funded by Development). When the workload is not busy, excess
resources are available for sharing as long as the workload is getting at
least 15% of the resources.
Workload. Development
Priority. 1
Usage goal. Match CPU allocation to consumption
Min CPU. 15 shares
Max CPU. 30 shares
When the Development workload becomes very busy, the following
priority 2 SLO enables the workload to borrow from other workloads that
may have excess resources. Because this SLO is priority 2, it is met only
after all priority 1 SLOs have been met. Based on usage patterns, the
SLO lets the workload borrow up to an additional 20 shares if available.
This allows the Development workload to access up to 50 CPU shares.
Workload. Development
Priority. 2
Usage goal. Match CPU allocation to consumption
Min CPU. 25 shares
Max CPU. 50 shares
Automatically resizing processor sets (PSETs)
With multiprocessor systems, you can isolate CPU resources for users or
applications by grouping processors together to form PSETs. WLM
allows you to define workloads based on PSETs. If you then specify SLOs
for these workloads, WLM automatically adjusts the number of
processors in the PSETs based on progress toward the SLOs. In this
example, the PSET workload Batch gets five processors, but only
between 10pm and 4am. At other times, Batch gets a minimum of one
processor by default.
Workload. Batch
Priority. 1
Usage goal. 500 CPU shares (5 cores)