Average CPU utilization was only 0.6 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.

The CPU was waiting for I/O an average of 2.5 percent of the time. This statistic does not indicate the presence of an I/O bottleneck. The time that the system was waiting for I/O peaked at 35 percent from 09:55:00 to 10:00:00.

The CPU was idle (neither busy nor waiting for I/O) and had nothing to do an average of 96.9 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.

The run queue had an average depth of 1.0 which indicates that processes were generally not bound by latent demand for CPU resources.

The peak run queue occupancy seen was 28 percent from 10:35:00 to 10:40:00. The following graph shows the both run queue length and occupancy. The occupancy is shown as %runocc/100, where a run queue occupied 100 percent of the time would be shown a vertical line reaching a height of 1.0.