|
|
Average CPU utilization was only 7.1 percent. This indicates that spare capacity exists within the CPU. If any performance problems were seen during the monitoring period, they were not caused by a lack of CPU power. CPU utilization peaked at 19 percent from 11:40:00 to 12:00:00. A CPU upgrade is not recommended because the current CPU had significant unused capacity.
The CPU was waiting for I/O an average of 0.8 percent of the time. This confirms the lack of a regularly occurring I/O bottleneck.
 The CPU was idle (neither busy nor waiting for I/O) and apparently had nothing to do an average of 92.2 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 cannot be considered by SarCheck. The run queue had an average depth of 1.4. This indicates that there was not likely to be a performance problem caused by processes waiting for the CPU. Average run queue depth (when occupied) peaked at 3.0 from 09:00:00 to 09:20:01. During that interval, the queue was occupied 3 percent of the time. The peak run queue occupancy seen was 3 percent from 13:20:00 to 14:00:00. The following graph shows both the run queue length and occupancy. The occupancy is shown as %runocc/10, where a run queue occupied 100 percent of the time would be shown a vertical line reaching a height of 10.0.
 |