mi...@cc.umanitoba.ca said: > What would I look for with mpstat? Look for a CPU (thread) that might be 100% utilized; Also look to see if that CPU (or CPU's) has a larger number in the "ithr" column than all other CPU's. The idea here is that you aren't getting much out of the T2000 if only one (or a few) of its 32 CPU's is working hard.
On our T2000's running Solaris-10 (Update 4, I believe), the default kernel settings do not enable interrupt-fanout for the network interfaces. So you can end up with all four of your e1000g's being serviced by the same CPU. You can't get even one interface to handle more than 35-45% of a gigabit if that's the case, but proper tuning has allowed us to see 90MByte/sec each, on multiple interfaces simultaneously. Note I'm not suggesting this explains your situation. But even if you've addressed this particular issue, you could still have some other piece of your stack which ends up bottlenecked on a single CPU, and mpstat can show if that's happening. Oh yes, "intrstat" can also show if hardware device interrupts are being spread among multiple CPU's. On the T2000, it's recommended that you set things up so only one thread per core is allowed to handle interrupts, freeing the others for application-only work. Regards, Marion _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
