HP-UX Workload Manager User's Guide

Example configuration files

manual_entitlement.wlm

Chapter 9 299

# Caveats:

# DO NOT MODIFY this file in its /opt/wlm/examples/wlmconf location!

# Make modifications to a copy and place that copy outside the

# /opt/wlm/ directory, as items below /opt/wlm will be replaced

# or modified by future HP-UX WLM product updates.

# Purpose:

# This example demonstrates the use of a parametric entitlement

# (allocation) to characterize the behavior of a workload. The user

# can directly set an allocation for a workload with wlmsend. By

# gradually increasing the workload’s allocation with a series of

# wlmsend commands, the operator can determine how the workload

# behaves with various amounts of CPU. This research can then be

# compared with similar data for the other workloads that will run on

# the system. This comparison gives you insight into which workloads

# you can combine (based on their needed CPU) on a single system

# and still achieve the desired SLOs. Alternatively, if you

# cannot give a workload its optimal amount of CPU, you will know

# what kind of performance to expect with a smaller allocation.

# The user’s workload is placed in grp1 and is associated with

# a metric called myapp.desired.allocation. The metric value

# represents an absolute allocation request as defined by the

# controlling SLO’s cpushares statement (see the definition for

# grp1 below).

# The workload is tested by sending a series of allocation requests

# like the following:

# % wlmsend myapp.desired.allocation 10