HP Process Resource Manager User's Guide

Fine-tuning your PRM configuration
Using prmanalyze to analyze your configuration
Chapter 8 165
group. If he is unrelated to any of the other activities on the machine, a
separate group with low CPU/memory shares (taken from the OTHERS
allocation) and a memory cap might be in order.
Example: High-level views of usage
The next example assumes a new multiprocessor machine in a university
environment. One way to get a very high-level view of usage is to request
a weekly or monthly report, setting the threshold so high that no details
come out. Because HP-UX limits accounting files to two Mbytes, several
files may need to be specified:
# prmanalyze -t weekly -d 16 *.acct98 Jan.acct99 Feb.acct99
weekly CPU report by command name begins at Thu Nov 5 13:48:00 1998
ave CPUs threshold 16.0
unique id ave CPUs peak CPUs total secs % total
Nov 1 0.00 0.00 0.00
Nov 8 0.00 0.02 1.61
Nov 15 0.01 1.11 4132.40
Nov 22 0.02 1.08 14136.57
Nov 29 0.02 1.53 9202.16
Dec 6 0.03 1.73 21125.86
Dec 13 0.02 0.75 14656.94
Dec 20 0.00 0.88 739.48
Dec 27 0.00 0.66 1243.89
Jan 3 0.00 0.63 2589.75
Jan 10 0.08 2.05 46000.07
Jan 17 0.09 7.58 53873.11
Jan 24 0.06 7.58 35398.47
Jan 31 0.07 9.34 68588.17
Feb 7 0.09 12.24 119510.85
One can see a definite progression here. Users gradually learn about the
new machine and try it out in 1998, with usage slacking over the holiday
break. Then, at the start of the first 1999 semester, usage increases
dramatically. At this rate, all 16 cores will be busy by next week. The
administrator needs to take definite steps to ensure all user groups have
a fair portion of the machine. Perhaps the department should even
consider ordering another system for the classes in question.