vmstat is great, but just one word of advice... I had some machines running AOLserver (damn good, but i found better and faster than him), and it had about 1024+ threads, and everything - ps, top, vmstat , which read the processes information in /proc , skewed a lot the information, because it took a lot of CPU (in the kernel, not in userspace). I haven't checked if that's changed with recent kernels (my last test was in 2.4.4, afaik, and in 2.5 there is a lot done about threads), but whatever you use to monitor the system, be sure that it doesn't affect it too much.
На вт, 2003-01-07 в 22:28, Adrian 'Dagurashibanipal' von Bidder записа: > On Tue, 2003-01-07 at 17:49, Russell Coker wrote: > > > Any suggestions? > > Monitoring vmstat output? I feel vmstat gives you all relevant data in > one place: memory, disk, cpu. > > Sorry, no advise on how to collect this from the network. > > cheers > -- vbi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
