HP Process Resource Manager User's Guide

PRM conﬁguration planning

Using prmanalyze to quickly identify resource use

Chapter 382

completion each day. It also gets its own PRM group. The next program,

web_broswer, also consumes a large amount of the CPU resources;

however, it is not a critical application and should not be allowed to

consume 16% of the CPU resource during peak periods. It needs to be

placed in its own PRM group to restrict its resource use. The forecasting

application sales_fcst deserves its own PRM group to ensure it gets

enough CPU resources. The last three applications are not consuming

signiﬁcant amounts of CPU resources and do not require their own PRM

groups.

Creating PRM groups for the applications mentioned above, then

assigning appropriate CPU shares, the new PRM conﬁguration is

represented by Table 3-2.

Step 3. Generate group/CPU records and application records to implement the

conﬁguration decided upon in Step 2.

Step 4. Use prmanalyze to create a summary CPU report, sorted by user and

piped to a reverse sort on the “% total” column to determine if there are

any critical users on the system that may require their own PRM groups:

# prmanalyze -s uid -r cpu -x root -p -t summary -1 filename | sort -r +5

The -x root combination prevents prmanalyze from showing data for

root processes, which typically are placed in the PRM_SYS group

(PRMID 0).

The output is omitted for brevity. However, assume the output shows

that most of the sales forecast data is entered by one or two users,

consuming approximately 3% of the CPU resources. For these users,

create user records with sales_fcst as the initial PRM group. Then

increase the CPU shares for sales_fcst from 15 to 18.

Table 3-2 Initial conﬁguration based on prmanalyze’s CPU report

Application PRM group CPU shares

mrkt_rsch Research 35

financials Finance 20

web_browser Web 5

sales_fcst Sales 15

All other applications OTHERS 25