HP-UX Workload Manager overview

11
Goal: 500 CPU shares (which corresponds to five cores)
Condition: Time is between 10:00 p.m. and 4:00 a.m.
Automatically resizing virtual partitions
HP virtual partitions enable you to partition a server, with each partition consisting of one or more
cores. Each virtual partition runs its own instance of the HP-UX operating system. With WLM, you can
automate the resizing of partitions.
Consider a system with two virtual partitions. The SLO for the Apps workload in partition 1 has a
higher priority than the SLO for the Dev workload in partition 0. When CPU usage for the Apps
workload in partition 1 reaches a certain point, WLM automatically migrates a core from partition 0
to partition 1 to satisfy the higher priority SLO of Apps.
Workload: Apps (partition1)
Priority: 1
Goal: Match CPU allocation to consumption
Workload: Dev (partition0)
Priority: 2
Goal: Match CPU allocation to consumption
Automatically resizing nPartitions using HP Instant Capacity cores
If you have HP Instant Capacity (iCAP) software configured on each partition, you can configure
WLM to “move” cores to the partitions where they are most needed. Given the hardware isolation,
the cores are not physically moved. WLM deactivates cores on one partition and then activates cores
on another partition, thereby giving the appearance of moving cores without incurring a charge for
an additional core.
Consider a system with two nPartitions, in which nPartition 0 runs the production, customer-accessible
version of a shopping website, while nPartition 1 runs the test version of this website. The SLO for the
Production workload on partition 0 has a higher priority than the SLO for the Test workload on
partition 1. When CPU utilization for the Production workload reaches a certain point, WLM
automatically migrates cores from nPartition 1 to nPartition 0 to satisfy the higher priority SLO.
Workload: Production (nPartition 0)
Priority: 1
Goal: Match CPU allocation to consumption
Workload: Test (nPartition 1)
Priority: 2
Goal: Match CPU allocation to consumption
Optimizing the use of HP Temporary Instant Capacity and HP Pay per use
If you have WLM on an HP Temporary Instant Capacity (TiCAP) system, you can configure WLM to
minimize the costs of using these resources by optimizing the amount of time the resources are used
for meeting the needs of your workloads.
Similarly, HP Pay per use (PPU) provides capacity as needed, basing payment on actual metered or
monitored use of that capacity. Using WLM with a system running a supported version of PPU, WLM
increases or decreases the capacity automatically, allocating the minimum number of cores needed to
satisfy SLOs. By minimizing the number of active cores, WLM reduces your costs.
You can use WLM to manage TiCAP or PPU on stand-alone systems, as well as across partitions. For
more information on using TiCAP or PPU with WLM, see “Using HP-UX Workload Manager with HP
Temporary Instant Capacity and HP Pay per use“ on page 24.