Hi,
A couple of months ago someone was asking about NFS performance on
Tru64 v5.x, I never saw any summary on the subject so I will bring it
up again.
I see very bad write performance with NFS3 clients running Tru64
versions 4.0G, 5.0A. and 5.1.
Clients running 4.0D or IRIX6.5 do not show this problem.
I have NFS servers running 4.0d PK4 and IRIX6.5.5, the problem remains
the same with the two servers. Both clients and servers are on Gigabit
connections.
For testing pure throughput I used
dd if=/dev/zero of=file_on_nfs bs=512
I see about 14MB/s using NFS2 and about 7MB/s using NFS3 with Tru64 5.1
On Tru64 v5.0A the figures are 7Mb/s - NFS2, 4MB/s - NFS3
this is with udp, using tcp is about 30% slower.
The throughput of NFS2 on 5.1 is acceptable for my application.
But, I have files that are larger than 2GB...
The real problem comes with opening and closing files.
Untaring a an archive with lots of small files (a few kb each)
takes about 1s per file using NFS3. This is totally unacceptable.
Using NFS2 untaring the same archive (containing only 200 files) is
done in less than a second.
As a curiosity - one of the exported filesystems is about 2TB in size.
Using df to view the filesystem size displays correct result with
NFS2!!! while NFS3 shows negative numbers.
As these machines are ES40s going back to 4.0D is not an option.
Does anyone know if 4.0F still had a working NFS?
If anyone could shed some light I'd be most grateful, I've tried
almost all paramters available to the mount command, related kernel
parameters and different operating systems for client and server.
Thomas
--
Thomas Eriksson thomas.eriksson_at_slac.stanford.edu
SSRL/Structure Molecular Biology Tel (650)926-4530 Fax (650)926-2258
2575 Sand Hill Rd. MS99
Menlo Park, CA 94025
Received on Sat Dec 16 2000 - 02:16:51 NZDT