Figure 9-24 shows common workload metrics we will combine with our Oracle and operating system analysis when building our response-time graphs and anticipating change. Figure 9-24 also provides two distinct informational aspects: the workload metrics in both seconds and milliseconds, and response-time-classified details. It provides these details by calculating the appropriate resource consumed (for example, CPU consumption) divided by the workload metric activity during the reporting interval. For example, each logical block processed consumed 0.01507 ms-that is, 0.01507 ms/lio. This is the logical IO service time and can be useful when constructing a response-time curve based on logical IO activity.

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.