HP Process Resource Manager User's Guide

PRM conﬁguration planning

Selecting a conﬁguration model

Chapter 374

Another way of allocating the computing resources equally is to assign

each department to an isolated area using PSET PRM groups. In the

following example, each department is allocated its own core for CPU

cycles. Memory is allocated equally using shares, and disk bandwidth is

obtained for the PSET PRM groups from PRM_SYS.

• User default group for guests and system administrator: 5 CPU

shares, 5 memory shares, 5 disk bandwidth shares

• Group A: Core 1, 50 memory shares

• Group B: Core 2, 50 memory shares

• Group C: Core 3, 50 memory shares

In the above example, you can also equally allocate memory shares using

memory isolation. The isolated groups will use only their entitlements.

They will not loan out or borrow memory from other groups.

NOTE Although the preceding example shows each department receiving one

core each, there is no requirement that these PSET PRM groups allocate

the same number of cores to each department. Core 0, however, is

reserved for FSS PRM groups within the default PSET.

Application priority model conﬁgurations

In an application priority model conﬁguration, you create PRM groups

and assign allocations that reﬂect the relative importance of the

application to your business as well as the resource needs of the

application. You can use tools such as prmanalyze, acctcom, and HP’s

GlancePlus to help you plan your conﬁguration.

For example, suppose you have three departments that use a system.

You have analyzed this system over a period of time and observed the

following list in order of descending priority:

• The sales department with ﬁve users running:

— Order process application

— Word processing and miscellaneous tasks

— Mail application