Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
performance:using-sysstat-to-track-system-performance [2011-06-09 14:57:41]
garrett.plasky Approved
performance:using-sysstat-to-track-system-performance [2011-06-09 14:58:06] (current)
garrett.plasky Approved
Line 48: Line 48:
  ​12:​40:​01 AM all 0.57 0.17 0.48 0.17 98.61  ​12:​40:​01 AM all 0.57 0.17 0.48 0.17 98.61
  ​12:​50:​01 AM all 0.45 0.19 0.44 0.06 98.87  ​12:​50:​01 AM all 0.45 0.19 0.44 0.06 98.87
- ​01:​00:​01 AM all 0.55 0.18 0.48 0.06 98.73</sh>+ ​01:​00:​01 AM all 0.55 0.18 0.48 0.06 98.73</sxh>
  
 Combined with the options listed above, you should be able to produce a report that you can use to diagnose slowing during a given period. The %user and %system columns simply specify the amount of time the CPU spends in user and system mode. The %iowait and %idle columns are of interest to us when doing performance analysis. The %iowait column specifies the amount of time the CPU spends waiting for I/O requests to complete. The %idle column tells us how much useful work the CPU is doing. A %idle time near zero indicates a CPU bottleneck, while a high %iowait value indicates unsatisfactory disk performance. Combined with the options listed above, you should be able to produce a report that you can use to diagnose slowing during a given period. The %user and %system columns simply specify the amount of time the CPU spends in user and system mode. The %iowait and %idle columns are of interest to us when doing performance analysis. The %iowait column specifies the amount of time the CPU spends waiting for I/O requests to complete. The %idle column tells us how much useful work the CPU is doing. A %idle time near zero indicates a CPU bottleneck, while a high %iowait value indicates unsatisfactory disk performance.