|
|
|
|
|
|
| Jprofiler |
| Optimize Java Performance - Performance Bottlenecks |
|
|
|
|
|
|
|
| Zoom in on Performance Bottlenecks |
|
| Controlling your application's performance may be driven by quality of service constraints or by general quality assurance, JProfiler's CPU views lend themselves naturally to both approaches. |
|
To record CPU data, you switch to the CPU section and click on the  recording button in JProfiler's tool bar. The first view in the CPU section shows the invocation tree, cumulated for all threads. To find performance related problem spots, just follow the big percentages when opening the tree nodes. Also, the absolute times and the number of invocations that are displayed for each node can help you in getting a feeling for the situation. Once you become familiar with JProfiler, you may want to customize this view to best fit your personal preferences. |
|
 |
|
| The invocation tree is a top-down view on the method calls of your application. This viewpoint is most useful when you experience an actual performance bottleneck in your application. If you want to improve overall performance, a bottom-up view may be more applicable. |
|
 |
|
This kind of view - called hot spots view - shows the methods where most of the time is spent. By opening these nodes you get backtraces which show the various invocation paths together with the percentages of their contributions. Note that by default, method calls within Java core classes are not shown separately - each of your library calls is treated as opaque. You can change this behavior by deactivating the corresponding filter sets |
|
|
|
|
|
|
|
|
