HP-UX Reference (11i v2 07/12) - 1 User Commands A-M (vol 1)

c
caliper(1)
For Integrity Systems Only
caliper(1)
Caliper 4.3 Caliper 4.3
(Requires Optional HP Caliper Software)
--system-usage=
{all|runstatus|syscalls|runstatus:syscalls
}
Controls the collection and reporting of system usage data. Two types of system usage data can be
collected:
runstatus (how much time each process spent running, eligible to run but not running,
and waiting),
syscalls (the count and time spent in every syscall called by a process), or
all (the
default).
No system usage data is collected or reported unless the option is used.
This measurement can be made in conjunction with any Caliper measurement. This option is only
available on HP-UX 11i v2 or later and with
--scope=process measurement runs.
--user-regions=default
|rum-sum
For runs involving the Itanium PMU, specifies whether the data should be collected for the entire run
(default), or only in regions delimited by the PMU enable/disable instructions (
rum-sum). For
more information, see Limiting PMU Measurements below.
When attaching to a process to perform
acount
, cgprof, fcount,orfcover measurements, the
dependent shared libraries of the program must be mapped as private before you can attach to the process.
You can enable private mapping of the shared libraries by using the
chatr command with the +dbg
enable
option on the program file (see chatr(1)). When attaching to a process for
acount, cgprof,
fcount,orfcover runs, caliper will remain attached to the target process until it exits (see also
--duration= SECONDS).
Stopping caliper with the use of SIGINT (e.g., Ctrl-C in a terminal window) for cgprof, fcount
,
fcover, and acount runs will result in all processes being forcibly terminated after Caliper generates a
performance report or writes data to a database.
CPU Metrics EVENT_SET Description
CPU Metrics measurement type requires HP-UX 11i V2 September 2004 OE (B.11.23.0409) or later. You
can specify the event sets and sampling period with the
--metrics and --sampling-spec
options,
respectively.
The
--cpu-aggregation=
COUNT option specifies how many samples will be aggregated into one
aggregated sample. You can measure multiple event sets in the same run. By default, the
overview
metrics consisting of the following 8 event sets will be measured: cpi, stall, dispersal
, l1icache,
l1dcache, l2cache, tlb, fp.
Example:
caliper cpu -o cpu.txt program
This will run program, measuring and reporting the following metrics by taking one sample every 8 mil-
liseconds: cpi, stall, dispersal, l1icache, l1dcache, l2cache, tlb, fp
. By default 125
low-level samples will be aggregated into one user-reported sample resulting in one aggregated sample col-
lected per second. The result is saved in the text file,
cpu.txt.
You can specify one or more comma separated list of predefined event sets. The following event sets are
available. overview is the default.
brpath Provides information on the dynamic mix of branch types, branch path distribution,
branch per instruction, etc.
brpred Provides metrics that are useful in assessing the effectiveness of branch prediction.
c2c Provides metrics related to cache coherence activity.
cpi Provides metrics related to Cycles Per Instruction (CPI)
cpubus Provides information on the demand that a specific CPU presents to the CEC chip set,
and the demand the CPU experiences due to the CEC traffic initiated by other CPUs
or I/O components in the system.
cspec Provides metrics on the effectiveness of control speculation.
dispersal Provides qualitative view of the parallelism that is available as seen at instruction
dispersal.
dspec Provides metrics on the effectiveness of data speculation.
l1dcache Provides miss rate information for the L1 data cache.
108 Hewlett-Packard Company − 18 − HP-UX 11i Version 2: December 2007 Update