[red]I am looking for feedback from experienced Linux admins regarding CPU usage analysis in Linux. The following should be taken in context of dual-CPU (Intel) systems with RedHat 7.2, kernel 2.4.7.10smp.[/red]
1) Has anyone seen issues with 'top' (from the procps package), where when the system has been up for more than about 200 days, top gives incorrect information and in fact core dumps when run!? (top from procps 2.07 -- yes, there are newer versions, but there glibc dependencies that prevent us from upgrading at this time.)
2) how far to you trust/believe top vs. vmstat, especially since that vmstat aggregates CPU information from all CPUs in an SMP system (correct?).
3) how useful is mpstat (from the sysstat package)? It's not part of our production environment now, and I would have to make the case to add it to hundreds of systems
Background is that I'm still somewhat new to Linux (but not UNIX), and we're seeing problems with top output, but I'm recommending the use of vmstat and mpstat based on my prev. experience in HP and Solaris.
Thanks in advance!
1) Has anyone seen issues with 'top' (from the procps package), where when the system has been up for more than about 200 days, top gives incorrect information and in fact core dumps when run!? (top from procps 2.07 -- yes, there are newer versions, but there glibc dependencies that prevent us from upgrading at this time.)
2) how far to you trust/believe top vs. vmstat, especially since that vmstat aggregates CPU information from all CPUs in an SMP system (correct?).
3) how useful is mpstat (from the sysstat package)? It's not part of our production environment now, and I would have to make the case to add it to hundreds of systems
Background is that I'm still somewhat new to Linux (but not UNIX), and we're seeing problems with top output, but I'm recommending the use of vmstat and mpstat based on my prev. experience in HP and Solaris.
Thanks in advance!