HP Process Resource Manager User's Guide

Fine-tuning your PRM conﬁguration

Using prmanalyze to analyze your conﬁguration

Chapter 8166

Example: Checking for patterns and conﬁguration

accuracy

In the following example, we assume a single-core system. Every so

often, it is a good idea to examine daily reports for patterns and

conﬁguration accuracy. For reports on recent data, it is a good idea to add

the -p ﬂag to catch jobs that never exit or that run for several days:

# prmanalyze -s prmid -r cpu -p -t daily -x 0 filename

daily CPU report by PRM id begins at Thu Jul 8 10:11:00 1999

ave CPUs threshold 0.01

unique id ave CPUs peak CPUs total secs % total

Jul 8 0.20 0.89 17280.72

1 0.02 0.55 1195.84 11.59

2 0.09 0.88 7439.40 43.08

3 0.05 0.56 4116.09 23.82

4 0.01 0.14 1226.88 7.11

5 0.03 0.17 2479.65 14.36

Jul 9 0.22 0.87 19008.00

1 0.02 0.60 2208.72 11.62

2 0.09 0.87 7890.23 41.51

3 0.06 0.60 4833.73 25.43

4 0.01 0.15 1699.32 8.94

5 0.02 0.14 2442.53 12.85

Jul 10 0.09 0.88 7996.40

1 0.00 0.10 193.63 2.42

2 0.09 0.88 7348.53 91.89

3 0.00 0.08 180.96 2.26

4 0.00 0.04 198.73 2.48

5 0.00 0.01 74.50 4.15

This daily report indicates that the CPU resources are idle most of the

time for this period. This is normal for a business that only uses its

computers from 9am to 5pm. During the week, the CPU resource usage

does not vary by more than about 10%, which is a good indication that

the current conﬁguration is working. However, the report for Saturday,

July 10th has what appears to be an anomaly. Group 2 is taking up