HP UX Caliper Software manual Module-Centric Reports

Table 8 Available Metrics for Report Sorting and Cutoffs (continued)

Report Name	Notes	Available Metrics
scgprof		• call-count

•msecs-per-call

•samples (default)

•seconds

traps Default by first trap • samples

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

----------------------------------------------

Metrics Summed for Entire Run

-----------------------------------------------

	PLM
Event Name	U..K	TH	Count
-----------------------------------------------
CPU_CYCLES	x___	0	79328752
BACK_END_BUBBLE.ALL	x___	0	35578366
BE_EXE_BUBBLE.GRALL	x___	0	14952374
-----------------------------------------------

Load Module Summary

-----------------------------------------------

% Total	Cumulat
IP	% of	IP
Samples	Total	Samples	Load Module
-----------------------------------------------
34.64	34.64	53	cc1
26.14	60.78	40	libc.so.6.1
22.88	83.66	35	libbfd-2.15.92.0.2.so
8.50	92.16	13	ld
3.27	95.42	5	ld-linux-ia64.so.2
2.61	98.04	4	as
1.31	99.35	2	gcc
0.65	100.00	1	*kernel gateway*
-----------------------------------------------
100.00	100.00	153	Total

-----------------------------------------------

Module-Centric Reports 107