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
Compiling and Linking Your Program
Preparing Your Program for Data Collection and Analysis
Using Dynamically Allocated Memory
Program Control of Data Collection
The C, C++, Fortran, and Java API Functions
Limitations on Data Collection
Limitations on Clock-Based Profiling
Runtime Distortion and Dilation with Clock-profiling
Limitations on Collection of Tracing Data
Runtime Distortion and Dilation with Tracing
Limitations on Hardware Counter Overflow Profiling
Runtime Distortion and Dilation With Hardware Counter Overflow Profiling
Limitations on Data Collection for Descendant Processes
Limitations on OpenMP Profiling
Experiments for Descendant Processes
Experiments on the Kernel and User Processes
Estimating Storage Requirements
Collecting Data Using the collect Command
-h counter_definition_1...[,counter_definition_n]
Collecting Data From a Running Process Using the collect Utility
To Collect Data From a Running Process Using the collect Utility
Collecting Data Using the dbx collector Subcommands
To Run the Collector From dbx:
Experiment Control Subcommands
Collecting Data From a Running Process With dbx on Oracle Solaris Platforms
To Collect Data From a Running Process That is Not Under the Control of dbx
Collecting Tracing Data From a Running Program
Collecting Data From MPI Programs
Running the collect Command for MPI
4. The Performance Analyzer Tool
5. The er_print Command Line Performance Analysis Tool
6. Understanding the Performance Analyzer and Its Data
You can collect performance data on user-mode targets in Performance Analyzer in several ways:
Using the collect command from the command line (see Collecting Data Using the collect Command and the collect(1) man page). The collect command-line tool has smaller data collection overheads than dbx so this method can be superior to the others.
Using the Oracle Solaris Studio Performance Collect dialog box in the Performance Analyzer (see “Collecting Performance Data Using the Collect Dialog Box” in the Performance Analyzer online help).
Using the collector command from the dbx command line (see Collecting Data Using the dbx collector Subcommands.
The following data collection capabilities are available only with the Oracle Solaris Studio Collect dialog box and the collect command:
Collecting data on Java programs. If you try to collect data on a Java program with the collector command in dbx, the information that is collected is for the JVM software, not the Java program.
Collecting data automatically on descendant processes.
You can collect performance data on the Oracle Solaris kernel using the er_kernel utility. See Chapter 9, Kernel Profiling for more information.