Figure 9-24. Shown is the workload diagnostic information. Notice only the total interval workload values and the interval (sample) time require entry. The workload information, combined with the ORTA, provides a plethora of diagnostic data we will use when anticipating performance solution impact.

Our ORTA shows response time can be significantly reduced by focusing on both physical block IO (queue time) and logical block IO (service time). To more clearly convey the situation and help others come to the same performance-enhancing conclusions as we have, we will create two response-time graphs: one focused on the CPU subsystem and the other on the IO subsystem.

Figure 9-25. Shown is a response-time graph created using OraPub's response-time graph template based solely on data shown in this example's related figures. This response-time graph focuses on the CPU subsystem, so we chose logical IO as our workload metric. As expected, the system is not operating in the elbow of the curve. Since there is virtually no queue time per logical IO processed, improving performance will be the result of decreasing service time or the number of logical IOs a SQL statement consumes.