HP UX Caliper Software manual Example 3 Example of a caliper diff Run

Example 3 Example of a caliper diff Run

================================================================================

HP Caliper 4.3.0 Difference Report Summary for Flat Profile

================================================================================

Collection Run 1: (Flat Profile)

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

Processor Information
Machine name:		fitzroy
Number of	processors:	4
Processor	type:	Itanium2 9M
Processor	speed:	1600 MHz
Virtual machine:		no

Run Information

Configuration:	/opt/caliper/config/fprof
Date:	January 05, 2007
Version:	HP Caliper - HP-UX Itanium Version 4.3.0
OS:	HP-UX B.11.23 U ia64
Database:	/home/sujoys/db1
Measurement scope: per-process
Sampling Specification
Sampling event:		CPU_CYCLES
Sampling period:		500000 events

Sampling period variation:		25000 (5.00% of sampling period)
Sampling counter privilege:		user (user-space sampling)
Data	granularity:	16 bytes
Data	sampled:	IP

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

Collection Run 2: (Flat Profile)

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

Processor Information
Machine name:		fitzroy
Number of	processors:	4
Processor	type:	Itanium2 9M
Processor	speed:	1600 MHz
Virtual machine:		no

Run Information

Configuration:	/opt/caliper/config/fprof
Date:	January 05, 2007
Version:	HP Caliper - HP-UX Itanium Version 4.3.0
OS:	HP-UX B.11.23 U ia64
Database:	/home/sujoys/db2
Measurement scope: per-process
Sampling Specification
Sampling event:		CPU_CYCLES
Sampling period:		500000 events
Sampling period variation:		25000 (5.00% of sampling period)
Sampling counter privilege:		user (user-space sampling)
Data granularity:		16 bytes
Data sampled:		IP

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

HP Caliper follows this algorithm:

1.The measurement type of the second database listed in the command is the only one that will be reported in the diff report output. (In other words, the second database listed is assumed to be the “base” database.)

2.All matching processes (of the measurement type of the second database specifier) in each database specifier are merged together, with data in the first database specifier essentially subtracted from data in the second database specifier.

3.The merged process data is diff'ed and reported.

You can create a diff report from two system-wide collection runs.

118 Controlling the Content of Reports