HP Caliper User's Guide

Table 9-2 Available Metrics for Report Sorting and Cutoffs (continued)
Available MetricsNotesReport Name
• call-count (Default)
Sorting only
fcount (HP-UX
only)
• address
• name
• reached_count
• reached_percent
• unreached_count
• unreached_percent (default)
fcover (HP-UX
only)
• avg-latency
• latency (default)
• sampled-misses
icache
• hpw-fills
• sampled-misses (default)
• soft-fills
itlb
• call-count
• msecs-per-call
• samples (default)
• seconds
scgprof
• samples
Default by first trap
traps
Module-Centric Reports
If you use the --group-by module option, HP Caliper will produce a module-centric
report. In a module-centric report, there is no data about individual processes in the
collection runs. Instead, all matching modules with data that can be merged are grouped
together, across processes.
For example, assume that you perform this HP Caliper run:
$ caliper fprof --group-by module cc himom.c
This produces a report similar to this (truncated) report:
====================================================
HP Caliper 4.3.0 Report Summary for Flat Profile
====================================================
Collection Run 1: (Flat Profile)
-------------------------------------
Processor Information
Machine name: jorasses
Run Information
Configuration: /opt/hp-caliper/config/fprof
140 Controlling the Content of Reports