Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Studio 12.3: Performance Analyzer Oracle Solaris Studio 12.3 Information Library |
1. Overview of the Performance Analyzer
3. Collecting Performance Data
4. The Performance Analyzer Tool
5. The er_print Command Line Performance Analysis Tool
6. Understanding the Performance Analyzer and Its Data
dbx Experiments That Create a Process
dbx Experiments on a Running Process
Interpreting Performance Metrics
Hardware Counter Overflow Profiling
Dataspace Profiling and Memoryspace Profiling
Call Stacks and Program Execution
Single-Threaded Execution and Function Calls
Function Calls Between Shared Objects
Overview of Java Technology-Based Software Execution
Java Call Stacks and Machine Call Stacks
Clock-based Profiling and Hardware Counter Overflow Profiling
User View Mode of Java Profiling Data
Expert View Mode of Java Profiling Data
Machine View Mode of Java Profiling Data
Overview of OpenMP Software Execution
User View Mode of OpenMP Profile Data
Expert View Mode of OpenMP Profiling Data
Machine View Mode of OpenMP Profiling Data
Mapping Addresses to Program Structure
Static Functions From Stripped Shared Libraries
Fortran Alternate Entry Points
Compiler-Generated Body Functions
Dynamically Compiled Functions
The <no Java callstack recorded> Function
The <Truncated-stack> Function
Functions Related to Hardware Counter Overflow Profiling
Mapping Data Addresses to Program Data Objects
The <Unknown> Data Object and Its Elements
Mapping Performance Data to Memory Objects
Index objects represent sets of things whose index can be computed from the data recorded in each packet. Index-object sets that are predefined include: Threads, Cpus, Samples, and Seconds. Other index objects may be defined either through the er_print indxobj_define command, issued directly or in a .er.rc file. In the Analyzer, you can define index objects by selecting Set Data Presentation from the View menu, selecting the Tabs tab, and clicking the Add Custom Index Object button.
For each packet, the index is computed and the metrics associated with the packet are added to the Index Object at that index. An index of -1 maps to the <Unknown> Index Object. All metrics for index objects are exclusive metrics, as no hierarchical representation of index objects is meaningful.