How WLM controls applications

WLM controls your applications after you isolate your applications in workloads based on:

To have resources migrated among workloads as needed, you create one or more SLOs for each workload. (In the case of nPartitions, which represent hardware, the core movement is simulated using Instant Capacity to deactivate one or more cores in one nPartition and then activate cores in another nPartition.) In defining an SLO, you specify the SLO’s priority. You can also specify a usage goal to attain a targeted resource usage. Or, if a performance measure (metric) is available, you can specify a metric goal. As the applications run, WLM compares the application usage or metrics against the goals. To achieve the goals, WLM automatically adjusts CPU allocations for the workloads.

For workload groups (which share the resources of a single HP-UX instance), WLM can manage each group’s real memory and disk bandwidth resources in addition to its CPU allocation.

	NOTE: WLM adjusts only a workload group’s CPU allocation in response to SLO performance. Thus, WLM SLO management is most effective for workloads that are CPU-bound.