Previous topic: Collecting performance data
Once you have collected performance data, you can analyze the result in the profiling tools to identify exactly what part of the code is causing the problem. Generally speaking, you will first narrow down the component (which application on which server) has the problem. Then, you can continue narrowing down to determine which package, class, and finally method is causing the problem. Once you know which method the problem is in, you can go directly to the source code to fix it.
Open the Logging and Profiling perspective (Window > Open Perspective > Other > Show All > Profiling and Logging) to use the profiling tools. Follow these steps to narrow down the location of the problem: