- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Understanding caliper scgprof report, term 'cycles...
Operating System - HP-UX
1752290
Members
4922
Online
108786
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2010 01:40 AM
03-15-2010 01:40 AM
Understanding caliper scgprof report, term 'cycles'
Hi,
We attached caliper to an exe in our environment and obtained the call graph profiles. (caliper scgprof)
The report has the below contents to say
Hot Call Paths (most likely)
----------------------------
% Total
Hits In
Only Name
----------------------------
7.8 libc.so.1::getenv [5]
libc.so.1::_index [6]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
6.8 [2]
*ROOT* [1]
----------------------------
[Minimum function entries: 5, percent cutoff: 1.00, cumulative percent cutoff: 100.00]
Further, in call graph listing, we see entries like "". What do these entries convey? What does the report mean when it says 'cycle # as a whole' without reference to any particular function (as seen in hot call path data given above).
Please help me understand the content of the report.
A block from call graph
-------------------------
[3] 14.6 0.00 795+8259 [3]
71.29 1062 libclntsh.so.10.1::ttcdrv [4]
8.58 352 libclntsh.so.10.1::sqlcxt [36]
5.97 890 libclntsh.so.10.1::kpuexec [47]
5.14 908+252 libclntsh.so.10.1::kpuexecv8 [56]
2.29 380+112 libclntsh.so.10.1::sqlcln [119]
2.28 930+1000 libclntsh.so.10.1::upirtrc [120]
1.18 314 libclntsh.so.10.1::sqlatm [192]
0.91 299 libclntsh.so.10.1::sqlcucExecute [230]
0.82 9 libclntsh.so.10.1::kpufch0 [249]
0.30 325 libclntsh.so.10.1::sqlnst [422]
0.23 313 libclntsh.so.10.1::sqlall [464]
0.19 943 libclntsh.so.10.1::nioqwa [509]
0.16 903 libclntsh.so.10.1::kpurcsc [553]
0.15 7 libclntsh.so.10.1::kpuexInitStmh [558]
0.15 922 libclntsh.so.10.1::OCIStmtExecute [563]
0.15 348 libclntsh.so.10.1::sqlopr [565]
0.06 4 libclntsh.so.10.1::sqlcucParse [783]
0.04 16 libclntsh.so.10.1::kpudSetDescInfo [908]
0.03 3 libclntsh.so.10.1::*unnamed@0x44(1fdd0-213f0)* [9
96]
0.03 34 libclntsh.so.10.1::kpusattr [1016]
0.02 8 libclntsh.so.10.1::kpuexCallback [1084]
0.02 3 libclntsh.so.10.1::sqlos2t [1115]
0.01 35 libclntsh.so.10.1::OCIAttrSet [1657]
0.01 7 libclntsh.so.10.1::OCIStmtFetch2 [1739]
0.00 9 libclntsh.so.10.1::sqlcucFetch [1858]
0.00 19 libclntsh.so.10.1::kpudcgcf [2511]
0.00 11 libclntsh.so.10.1::kpufch [2560]
-----------------------------------------------
Thanks!
We attached caliper to an exe in our environment and obtained the call graph profiles. (caliper scgprof)
The report has the below contents to say
Hot Call Paths (most likely)
----------------------------
% Total
Hits In
Only Name
----------------------------
7.8 libc.so.1::getenv [5]
libc.so.1::_index [6]
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
6.8
*ROOT* [1]
----------------------------
[Minimum function entries: 5, percent cutoff: 1.00, cumulative percent cutoff: 100.00]
Further, in call graph listing, we see entries like "
Please help me understand the content of the report.
A block from call graph
-------------------------
[3] 14.6 0.00 795+8259
71.29 1062 libclntsh.so.10.1::ttcdrv
8.58 352 libclntsh.so.10.1::sqlcxt
5.97 890 libclntsh.so.10.1::kpuexec
5.14 908+252 libclntsh.so.10.1::kpuexecv8
2.29 380+112 libclntsh.so.10.1::sqlcln
2.28 930+1000 libclntsh.so.10.1::upirtrc
1.18 314 libclntsh.so.10.1::sqlatm
0.91 299 libclntsh.so.10.1::sqlcucExecute
0.82 9 libclntsh.so.10.1::kpufch0
0.30 325 libclntsh.so.10.1::sqlnst
0.23 313 libclntsh.so.10.1::sqlall
0.19 943 libclntsh.so.10.1::nioqwa
0.16 903 libclntsh.so.10.1::kpurcsc
0.15 7 libclntsh.so.10.1::kpuexInitStmh
0.15 922 libclntsh.so.10.1::OCIStmtExecute
0.15 348 libclntsh.so.10.1::sqlopr
0.06 4 libclntsh.so.10.1::sqlcucParse
0.04 16 libclntsh.so.10.1::kpudSetDescInfo
0.03 3 libclntsh.so.10.1::*unnamed@0x44(1fdd0-213f0)*
96]
0.03 34 libclntsh.so.10.1::kpusattr
0.02 8 libclntsh.so.10.1::kpuexCallback
0.02 3 libclntsh.so.10.1::sqlos2t
0.01 35 libclntsh.so.10.1::OCIAttrSet
0.01 7 libclntsh.so.10.1::OCIStmtFetch2
0.00 9 libclntsh.so.10.1::sqlcucFetch
0.00 19 libclntsh.so.10.1::kpudcgcf
0.00 11 libclntsh.so.10.1::kpufch
-----------------------------------------------
Thanks!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2010 03:33 AM
03-15-2010 03:33 AM
Re: Understanding caliper scgprof report, term 'cycles'
Cycles typically means recursions.
>"". What do these entries convey?
It probably means all of the recursive functions, taken as a whole, account for that percentage.
>"
It probably means all of the recursive functions, taken as a whole, account for that percentage.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP