HP UX Caliper Software manual Performing CPU Metrics Analysis, 151

12 Performing CPU Metrics Analysis

HP Caliper can measure and report per-process or system-wide metrics based on sampled CPU events. This is enabled by the cpu measurement.

Specify the events and sampling period with the -mevent_set and -speriod options, respectively. You can measure multiple metrics in the same run.

For most applications, the cpu measurement is the first measurement you should take when you begin using HP Caliper. Run this command:

$ caliper cpu -o cpu.txt program

This will run program, using the default event set of overview and measuring and reporting the following metrics by taking one sample every 8 milliseconds: stall, cpi, dispersal, l1icache, l1dcache, l2cache, tlb, and fp. By default, 125 low-level samples will be aggregated into one user-reported sample, resulting in one aggregated sample collected per second. The result is saved in the text file cpu.txt.

For Integrity servers dual-core Itanium 2 and Itanium 9300 quad-core processors, the default event set of overview measures and reports these metrics: stall, cpi, dispersal, l1icache, l1dcache, l2icache, l2dcache, l3cache, tlb, and fp.

For a system-wide cpu measurement, run this command:

$ caliper cpu -w -e 120 -o cpu.txt

This will collect system-wide overview CPU measurements for two minutes and save the result in the text file cpu.txt.

The cpu measurement is the only HP Caliper measurement that makes use of multiplexing.

For more information, with additional examples of how to use the cpu measurement and a listing

of the available event sets, see “cpu Measurement Report Description ” (p. 178).

For details about the event sets, see “Event Set Descriptions for CPU Metrics ” (p. 219).

151