| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Studio 12.2: Performance Analyzer |
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
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 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
By default, collect requires its target to be an ELF executable and checks the target to verify this. However, you can disable this check and enable collect to run on a script that you specify as the target.
Note - Script profiling is considered an experimental feature. The implementation may change in a subsequent release.
To profile a script, you first set the environment variable SP_COLLECTOR_SKIP_CHECKEXEC to disable the checking for an ELF executable.
By default, data is collected on the program that is launched to execute the script and on all descendant processes. To collect data only on a specific process, use the -F flag to specify the name of the executable to follow. For example, to profile the script foo.sh, but collect data primarily from the executable bar, use the following commands.
For csh:
% setenv SP_COLLECTOR_SKIP_CHECKEXEC % collect -F =bar foo.sh
For sh:
$ export SP_COLLECTOR_SKIP_CHECKEXEC $ collect -F =bar foo.sh
Data is collected on the founder process that is launched to execute the script, and on all bar processes that are spawned from the script, but not collected for other processes.
|