HP-UX Workload Manager Toolkits User's Guide

HP-UX WLM Duration Management Toolkit and HP-UX WLM Toolkit for Base SAS Software
Overview of how WLM’s duration management works
Chapter 6108
Overview of how WLM’s duration
management works
Before you can manage duration, you need profile values for your
applications. These values represent the CPU time needed by your
application to complete. You can get these values as explained in
“Completing an application within a certain duration (duration
management)” on page 114. You also need to create a discovery command
to identify each application you plan to manage. Each discovery
command, which runs exactly once during the life of its target
application, will determine the PID of its target application. This
command then outputs the PID, the profile value, and the desired
duration for its target application. The duration data collector wlmdurdc
takes the information from the discovery command, does some
calculations, then feeds the result into WLM. Next, WLM determines a
new CPU allocation for the workload group containing the target
application. This allocation is based on whether the application is going
to complete too quickly or too slowly. If the application is on schedule to
complete at the desired duration, WLM simply attempts to maintain the
current CPU allocation. Figure 6-3 illustrates this process. The graphic
applies to any environment where SAS jobs do not exist or are not
instrumented with the macro hp_wlmtk_goals_report.