HP-UX Workload Manager User's Guide

WLM quick start: the essentials for using WLM
How to determine a goal for your workload
Chapter 2 87
# /opt/prm/bin/prmmove surfers -p 4065
Default: Inheriting workload group of parent process
If a process is not named in an apps statement, a users statement, a
uxgrp statement, or an scomp statement, or if it is not identified by a
procmap statement, or has not been started with prmrun or moved with
prmmove, it simply starts and runs in the same group as its parent
process. So for a setup like the following example, if user jdoe has an
interactive shell running in group mygrp, any process spawned by that
shell process would also run in group mygrp because its parent process
was there.
prm {
groups = OTHERS : 1,
mygrp : 2;
}
Simple inheritance is the mechanism that determines where most
processes run, especially for short-lived processes.
How to determine a goal for your workload
NOTE Be aware of the resource interaction for each of your workloads. Limiting
a workload’s memory allocation can also limit its CPU use. For example,
if a workload uses memory and CPU resources in the ratio of 1:2,
limiting the workload to 5% of the memory implies that it cannot use
more than 10% of the CPU resources —even if it has a 20% CPU
allocation.
To characterize the behavior of a workload, use the following example
WLM configuration (to see the contents of the configuration file, see
“manual_entitlement.wlm” on page 298):
/opt/wlm/examples/wlmconf/manual_entitlement.wlm