User's Manual

Table Of Contents
Figure 4 Prioritizing resource use for an application
GroupA
User1
User2
Process1
Process2
Process3
50%
25%25%
GroupB
Critical application
and its child processes
HP-UX server
GroupC
Limiting resource consumption
The following example describes a situation where a system administrator needs to limit resource
consumption.
A system administrator has determined that screen savers displaying fractal designs consume as
much CPU resource as permitted. To protect the system from these screen savers during the work
day, the administrator creates a PRM group for them. This PRM group limits CPU consumption—when
the system is at peak load—to 5%. When the system is not fully utilized, the screen savers can use
the available CPU resources. Whenever the CPU cycles are needed for productive work, the screen
savers cannot use more than 5% of the CPU resources.
Isolating resource use for applications and users
The following example describes a situation where a system administrator needs to isolate an
application in order to ensure dedicated memory and CPU cycles.
A system administrator has determined that his company’s credit card purchase system needs
dedicated memory and CPU resources for users who are buying products. To ensure the buyers
dedicated CPU cycles, the system administrator creates a PSET PRM group for buyers and assigns
one of the system’s four cores to the group. This guarantees the CPU cycles will be available to
buyers as needed. In addition, the system administrator chooses the memory isolation option to
prevent memory shares from being loaned out or borrowed from other groups. This ensures
immediate response time, rather than waiting for borrowed memory to be paged back in.
16 Overview