Memory Usage
previous next
One of the hardest bottlenecks to identify is insufficient physical memory. SarCheck will help you to detect a shortage of physical memory by analyzing a number of different statistics and reporting its conclusions.

 

There was no indication of swapped out processes in the ps -elf data. Processes which have been swapped out are usually found only on systems that have a very severe memory shortage.

The average number of page replacement cycles per second (cycle/s) was 0.083. The number of page replacement cycles per second peaked at 0.39 from 13:55:01 to 14:00:00. Peak resource utilization statistics can be used to help understand performance problems. If performance was worst during the period of peak replacement cycle activity, then a shortage of physical memory may be performance bottleneck.

The average number of kernel threads waiting to be paged in (swpq-sz) was 3.50. The average number of kernel threads waiting to be paged in (swpq-sz) peaked at 17.6 from 14:55:00 to 15:00:00. When the peak was reached, the swap queue was occupied 100 percent of the time. A more useful statistic is sometimes available by multiplying the swpq-sz data by the percent of time the queue was occupied. In this case, the average was 1.70 and the peak was 17.60 from 14:55:00 to 15:00:00. Peak resource utilization statistics can be used to help understand performance problems. If performance was worst when the number of kernel threads waiting to be paged in was at its peak, then a shortage of physical memory may be performance bottleneck.