Section 11.1. Beyond the Resource Profile

---

11.1 Beyond the Resource Profile

The resource profile is an excellent first step that allows you to target the right piece of a user action's response time for detailed analysis. But once you understand which response time component dominates your user action's response time, what do you do next ? The answer is simple:

Find the source text (the SQL or PL/SQL) of the cursor that contributes the most to the duration of the component.

Doing this with extended SQL trace data is straightforward, as I explain in Section 5.6. Once you have found the SQL text of the first cursor action that contributes the most to your top response time component duration, you're well on the way to constructing a remedy. Your next step is to learn why the source code you've found motivates so much time spent at this component. The next section describes how to find out.

---

Top