Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Studio 12.2: Simple Performance Optimization Tool (SPOT) User's Guide |
1. The Simple Performance Optimization Tool (SPOT)
2. Running SPOT on Your Application
Runtime System and Build Information
Analysis of Application Stall Behavior Section
Maximum Resources Used By The Process Section
Pairs of Top Four Stall Counters Section
Application HW Counter Profile Output
Summary of Key Experiment Metrics Table
Here are some final things to be aware of when using SPOT reports:
All of the data and commands used to generate a report are recorded in the same directory as the report.
Each SPOT run directory contains a Performance Analyzer experiment (test.1.er) that is used to generate the run profile. You can load this experiment into the Performance Analyzer or the er_print tool if further investigation of the profile is necessary.
The SPOT run directory contains log files for the various stages of the run. These log files report any error conditions that were encountered. The debug.log file contains a transcript of all of the commands used to generate the run report.
The SPOT run report contains information that might be considered confidential, so take care in handling the report. Examples of information that the report might contain are:
The spot command that ran the binary.
The location of the binary and where it was run.
The location of the compiler used to build the binary.
The source code files that contain routines where significant time was spent.