Working with the Profiled Data
Use
When the application is started in profiling mode and you have run it and performed several invocations in particular areas to detect a possible problem, you can then browse through packages, methods, invocations and objects to find the problem area.
Prerequisites
You must have started the application in a profiled mode. For more information, see Start Profiling.
Procedure
If you want to |
Then |
Browse the package structure of an application |
... 1. Choose the Tree View option. The packages, classes and methods are displayed with different icons. The available columns for them are: a. Average net time – these values are available only for methods b. Net time – these values are available only for methods c. Gross time d. Invocation count When a package, a class, or a method is selected, the corresponded invocations are displayed in the Invocation table below. |
Display only the methods of an application |
... 1. Choose the Table View option. The possible actions here are: a. Sorting by all columns b. Filtering by method name When a method is selected, the corresponding invocations are displayed in the Invocation table below. |
View invocations |
... Invocations can be viewed when you select a package, a class, or a method from one of the steps described above. All invocations for the selected type are listed. The possible actions here are: · Sorting – by method name, start time of the invocation, net time and gross time. Only top invocations are sorted · Browsing invocation stack |
Viewing objects |
Objects can be viewed when you select an invocation as it is described in the View invocations case above. The possible objects for browsing are: · This pointer · Method arguments · Method return value |