Optimising NFS for system files

Bernard Dugas bernard at dugas-family.org
Tue Dec 30 21:39:56 UTC 2008

Wojciech Puchar wrote:
>>> This is a Gbps network with only 1 switch between nfs server and
>>> client, with less than 0.2ms ping. So bandwidth should not be a
> it should work with near-wire speed on 100Mbit clients.

Server and clients are 1Gbps.

But i have a 4 factor of performance for reading only ...

nfsserver# time tar -cf - clientusr-amd64 > /dev/null
5.001u 12.147s 1:23.92 20.4%    69+1369k 163345+0io 0pf+0w

client9# time tar -cf - /usr > /dev/null
tar: Removing leading '/' from member names
3.985u 19.779s 4:32.47 8.7%     74+1457k 0+0io 0pf+0w

Note : clientusr-amd64 is around 1.3GB and is the same directory 
exported to client9 /usr with nfs.

I have tried on 7.1-RC1 and 7.1-RC2, with amd64 architecture.

CPU don't seem to be the limiting factor, more than 80% idle on server, 
they are either Core2duo on nfsserver :
Dec 23 04:52:18 nfsserver kernel: CPU: Intel(R) Celeron(R) CPU 
E1200  @ 1.60GHz (1600.01-MHz K8-class CPU)
Dec 23 04:52:18 nfsserver kernel: Origin = "GenuineIntel"  Id = 0x6fd 
Stepping = 13

or on client9 :
/var/log/messages.3:Dec 29 12:21:20 client9 kernel: CPU: Intel(R) 
Core(TM)2 Duo CPU     E4500  @ 2.20GHz (2200.01-MHz K8-class CPU)

If anybody can help to look at right places... ? How may i divide the 
problem ?

Or is my simple test wrong ? I use a tar directed to /dev/null to avoid 
any writing.

Best regards,
Bernard DUGAS Mobile +33 615 333 770

More information about the freebsd-questions mailing list