HP XC System 3.x Software - Manual (Page 46)

Viewing Per-Procedure Data: hpcpiprof image_name
If you run hpcpiprof with an image name, it displays statistics for the image, partitioned
per-procedure. For example:
% hpcpiprof myApp
myApp: not found.
+ Found and using /var/users/who1/bin/myApp
-------
Event Name Events Period Samples
---------- ------------- ------ --------
CPU_CYCLES 1925103240000 60000 32085054
CPU_CYCLES % cum% procedure image
---------- ----- ------ ----------- -----
191201e7 99.3% 99.3% routine1 myApp
1309e7 0.7% 100.0% unknown_rou myApp
The output is described in the following sections.
HPCPI Procedure Header
The header uses the common HPCPI format, as described in “HPCPI Header” (page 44) , with
the following differences:
• The utility searches for a binary file with the specified image name and a checksum value
that matches the checksum value for the image that generated the event data.
In this example, myApp is a relative pathname and the file is not in the current directory.
The message myApp: not found indicates that hpcpiprof did not find the image myApp
in the current directory with the appropriate checksum value.
The message + Found and using /var/users/who1/bin/myApp indicates the full
path of the binary it found.
• The event count and sample values are relative to the events recorded for the image.
hpcpiprof Procedure Data Table
The data table for procedure data uses the format as described in “hpcpiprof Image Data Table”
(page 44) , with the following differences:
• The column procedure contains the procedure name. The procedure name unknown_rou
represents events that can not be attributed to a specific routine. For more information, see
“HPCPI Product Limitations” (page 115) .
• The values in each entry are relative to the events recorded for the procedure in the image.
46 Using HPCPI