RESOURCE ANALYSIS SECTION

Average CPU utilization (%usr + %sys) was only 23.1 percent. This indicates that spare CPU capacity exists. If any performance problems were seen during the entire monitoring period, they were not caused by a lack of CPU power. User CPU as measured by the %usr column in the sar -u data averaged 18.3 percent and system CPU (%sys) averaged 4.7 percent. The sys/usr ratio averaged 0.26 : 1. CPU utilization peaked at 75 percent from 16:00:00 to 16:05:00. Peak resource utilization statistics can be used to help understand performance problems. If performance was worst during the period of peak CPU utilization, then a performance bottleneck may be the CPU.

The CPU was waiting for I/O (%wio) an average of 17.4 percent of the time. This statistic does not indicate the presence of an I/O bottleneck. In at least one quarter of the samples, more than 20 percent of the CPU's time was spent waiting for disk I/O. The time that the system was waiting for I/O peaked at 73 percent from 14:50:00 to 14:55:00. Peak resource utilization statistics can be used to help understand performance problems. If performance was worst during the period when the system was waiting for I/O, then a performance bottleneck may be caused by processes waiting for I/O.

The CPU was idle (neither busy nor waiting for I/O) and had nothing to do an average of 59.5 percent of the time. If overall performance was good, this means that on average, the CPU was lightly loaded. If performance was generally unacceptable, the bottleneck may have been caused by remote file I/O which cannot be directly measured with sar and therefore cannot be considered by SarCheck.