|
Rahul,
Here's what I would do.
1) I would use "mpstat" for the processor statistics. This breaks the
usage up by processor in SMP configurations. This can be useful to see the
relative loading of each CPU, in particular the breakdown of kernel and user
time.
2) Memory: Concentrate on Page Outs and Free Memory more than anything
else. That will give you plenty of clues about memory starvation, and the
relevence of your VM tuning.
3) I/O: User "sar -d". It's a bit annoying on a system with a lot of
disks, because it returns a row for every device, even if no I/O occurred in the
sample period. However, it makes it easier to parse. ;-) Notably, keep an eye on
the Service Times (avserv?), Wait times (avwait), and the queue depth. The
utilisation is a function of these (queuing theory), but you can store that too
as a shortcut. You can give sar any sample period, so your 5 minute averages are
no problem.
4) Network: "netstat 5" will report a row for every 5 seconds (for
example), showing how many packets went in and out of each interface. Your
question below is easily answered - you have two columns in your output; the
first is for the named interface (hme0), the 100baseT network card. The second
is a total of all cards - looks like you only have one. This total can also
include the loopback interface (lo0), so look out for that.
Good luck, you're doing the right thing. I've been working on some
software to do just this for a couple of years. I'd love to hear how it
goes!
Regards
James
--
James Morle Scale Abilities, Ltd http://www.scaleabilities.co.uk Author of "Scaling Oracle8i - Building Highly Scalable OLTP System Architectures"
|
Title: Message
- RE: [Fwd: UNIX Performance Issues] James Morle
- Re: [Fwd: UNIX Performance Issues] Rahul Dandekar
- RE: [Fwd: UNIX Performance Issues] James Morle
- RE: [Fwd: UNIX Performance Issues] James McCann
- Re: [Fwd: UNIX Performance Issues] Rahul Dandekar
- RE: [Fwd: UNIX Performance Issues] James Morle
- RE: [Fwd: UNIX Performance Issues] Post, Ethan
