Andrew Gideon <(E-Mail Removed)> writes:
>
>I've a couple of projects where network performance is an issue: a NAS
>and a Router. Both are actually clusters, but I'm pretty sure that
>that's beside the point (though I mention it Just In Case {8^).
>
>The NAS is is actually a "head", speaking NFS on the front and iSCSI on
>the back. The router is the usual IP device.
>
>Everything works using the built-in GigE interfaces. But I'm thinking
>that I can squeeze more performance out of my boxes if I push more of the
>processing out of the system and onto the network interface cards.
>So...any suggestions?
Some experimental data:
The setup: The NFS server is a 2.66GHz Pentium 4 with an onboard Intel
e1000 interface; the data is a directory containing 354112 KB of
files. I first warmed up the NFS server's cache by reading this data
on a machine that I did not use later in the test. Then I read the
data on various machines with:
time tar cf - <dir> |cat >/dev/null
Running this on a 3GHz Xeon 5160 machine with an Intel e1000
interface:
real 0m5.163s
user 0m0.044s
sys 0m0.364s
A 2GHz Opteron 246 machine with a Tigon3 interface:
real 0m5.226s
user 0m0.102s
sys 0m1.693s
An Opteron 270 machine running at 1GHz (clocked down) with a Tigon3 interface:
real 0m4.959s
user 0m0.080s
sys 0m1.760s
A 2.2GHz Athlon 64 X2 4400+ machine with an Nvidia (forcedeth) interface:
real 0m4.956s
user 0m0.040s
sys 0m1.196s
An Athlon 64 X2 4600+ machine running at 1GHz (clocked down) with an
Nvidia (forcedeth) interface:
real 0m5.012s
user 0m0.076s
sys 0m2.180s
All these machines run a 2.6.18 kernel, except the Opteron 246
(2.6.10) and the NFS server (2.6.13).
Looks like the e1000 produces the least CPU load, but none of these
cards produce so much CPU load that you need to worry about it if the
machine is a dedicated NFS server.
I also watched the NFS server with top during one of these jobs, and
the load stayed low.
Note also that having all the data cached on the NFS server is a
worst-case setting for CPU load; more typically the server will wait
much of the time for disk seeks to complete.
>The one absolute requirement in both cases is that I not lose the ability
>to "speak" 802.1q to a switch.
I cannot help you there. I don't know what 802.1q is.
Followups set to comp.os.linux.hardware.
- anton
--
M. Anton Ertl Some things have to be seen to be believed
(E-Mail Removed) Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html