HP-UX Workload Manager User's Guide

Advanced WLM usage: Using performance metrics
Configuring WLM for metric-based SLOs
Appendix H474
Consider using absolute_cpu_units (discussed in
“Using absolute CPU units” on page 217) to minimize
the effects of a system’s variable number of CPU
resources on your offset value.
Here are some request_value expressions and the corresponding
cpushares statements:
request_value = 25
cpushares = 25 total;
request_value = 10 * X + 30
cpushares = 10 total per metric X plus 30;
Consider the following example of an additive allocation request:
slo additive_example {
pri = 1;
mincpu = 0;
maxcpu = 50;
entity = PRM group App1;
cpushares = 5 more per metric application_procs;
}
Assume this is App1’s only SLO at this priority. Also assume gmincpu is
20 and application_procs (the number of processes the application has
running) is 3. The SLO requests 35 CPU shares: 5 shares for each of the
3 processes the application has running plus 20 shares from gmincpu.
The next example shows an absolute allocation request. It is the same as
the previous additive example—except it uses total in place of more.
slo absolute_example {
pri = 1;
mincpu = 0;
maxcpu = 50;
entity = PRM group App1;
cpushares = 5 total per metric application_procs;
}
Again, assume application_procs is 3. This time, because it is an absolute
request, the request starts from 0, not the previous allocation request.
Consequently, the request is 5 CPU shares for each of the 3 application
processes in workload group App1 for a total of 15. However, the request
is ignored because the group already has 20 shares because of its
gmincpu setting.