This example is designed to demonstrate the main features of the Performance Analyzer and some performance analysis tasks using five programming scenarios. To do the tutorial, you must first collect performance data. See Collecting Data for the synprog Example for instructions. Then choose from the following scenarios:
-
"Simple Metric Analysis" demonstrates the function list, the annotated source code listing and the annotated disassembly code listing to do a simple performance analysis of two routines that shows the cost of type conversions.
-
"Metric Attribution and the gprof Fallacy" demonstrates the Callers-Callees tab and shows how time that is used in a low-level routine is attributed to its callers. gprof is a standard UNIX performance tool that properly identifies the function where the program is spending most of its CPU time, but in this case wrongly reports the caller that is responsible for most of that time.
-
"The Effects of Recursion" shows how time is attributed to callers in a recursive sequence for both direct recursive function calls and indirect recursive function calls.
-
"Loading Dynamically Linked Shared Objects" demonstrates the handling of load objects and shows how a function is correctly identified even if it is loaded in different locations at different times.
-
"Descendant Processes" demonstrates the use of the Timeline tab and filtering to analyze experiments on a program that creates descendant processes.
Can't find what you are looking for?
Submit your comments at http://www.sun.com/hwdocs/feedback.
Legal Notices