HP Caliper User's Guide

If you specify --module-default none, then HP Caliper uses only files specified
in the --module-include list.
For example, if you only want to include libc in a measurement, you would use these
options:
--module-default none --module-include libc
Controlling Granularity of Data Collection and Reports
You can control the granularity of data collection and reports. If you want finer
granularity (that is, more samples), use the -s option to lower the number of events
between samples. For example, you can change the rate from the default 500,000 cycles
to 250,000 cycles to get more samples. However, the increased sampling might have a
negative effect on your application's performance.
If your program is likely to have repeating patterns, such as loops, those patterns might
coincide with the fixed sampling rate, affecting the results. For example, some functions
might not be sampled because the IP is never in the function on the measurement cycle.
A solution for this is to vary the sampling rate by some number of cycles.
For more information, see “-s or --sampling-spec” (p. 69).
Specifying Processes to Measure
The -p option allows you to measure only the parent (that is, the root) process, selected
processes in a process tree, or all processes that are spawned. In addition, HP Caliper
provides several ways to treat processes. You can:
• Measure the selected processes
• Track the processes without measuring them in order to identify interesting child
processes
• Ignore specific processes
By default, HP Caliper measures and reports on the parent process and all child
processes, including native Integrity servers-based processes started by PA-RISC-based
binaries running in emulation mode. HP Caliper, however, does not measure the
PA-RISC binaries themselves.
To measure the parent process alone, use the -p root option.
By default, HP Caliper produces separate reports for each process and concatenates
them to stdout or the output file specified in the -o (or --output-file) option.
If you want a separate file for each report, use the -o option with its per-process
modifier. (See “-o or --output-file” (p. 67).) This option produces files that use this
naming convention:
basename.executablename
For example, the following command on HP-UX:
$ caliper fprof -o COUT,per cc foo.c
Configuring Data Collection 127