We collected the following database performance data through the Oracle database AWR report.
Based on the 20-minute AWR reports of a test case, the IOPS is the sum of physical read total I/O requests, per Second, and physical write total I/O requests, per Second, as shown in the following figure.
Figure 37. Sample of IOPS measurement from AWR report
For an Oracle OLTP-style I/O workload, db file sequential read, the User I/O class wait is always the top wait event, accounting for most of the wait time. In this example, wait time averaged 0.443 milliseconds, as shown in the preceding figure.
In addition to db file sequential read wait event, transaction redo logging write is another key performance indicator for Oracle OLTP-style I/O workloads. The following figure shows the top five timed events section of the AWR report from one of the OLTP production databases while the workload ran. In this example, wait time averaged 0.244 milliseconds.
Figure 38. Example I/O Latency measurement from AWR report
For an Oracle OLAP-style I/O workload, the I/O MB/s throughput can be calculated as the physical read total I/O bytes per second, as shown in the following figure. In this example, the I/O throughput is 591,947,981.72 bytes per second, or 564.52 MB/s.
Figure 39. Sample of I/O throughput in MB/s from AWR report
The CPU utilization of the database nodes is shown in the OS Statistics By Instance field of the AWR report, as shown in the following figure.
Figure 40. Example CPU Utilization measurement from AWR report