topic Re: NFS in Operating System - HP-UX

NFS

Tony Lowrie — Wed, 18 Oct 2000 09:37:57 GMT

Why does a large distance(200 miles) between an NFS server and client cause so many performance problems ?

Re: NFS

CHRIS_ANORUO — Wed, 18 Oct 2000 10:43:59 GMT

The distance should not affect the NFS performance, it is the nature/quality of your link between the servers that you have to put into cosiderations.

Re: NFS

Trevor Dyson — Wed, 18 Oct 2000 10:46:07 GMT

Hi,
Without more information about your particular environment the standard answer would have to be that there must be some WAN links involved over a distance of 200 miles and that the performance of NFS over this distance will be impacted most by the slowest WAN link in place betweens the sites involved. Traffic prioritisation may be a factor as well, i.e. routers may have been configured to place a lower priority on NFS traffic in relation to more interactive or OLTP related traffic, eg telnet etc.

Maybe NFS is not the best method for achieving you data transfer requirements.

Regards, Trevor

Re: NFS

Paul McCleary — Wed, 18 Oct 2000 11:03:30 GMT

Distance might not be the problem, you should also consider:

client-server ratio, has it increased recently
what the shared apps are
what the nfs server spec is and what else is it doing
what is the network link load/reliability

If the problem is due to distance it might be due to the NFS process. The client has to ask the server what port mountd is running on it reponds; client then asks mountd for the filehandle for a specific file you've requested; server responds; then with this filehandle the client asks the portmapper what nfsd to use; server responds; client then queries the nfsd with the filehandle and it provides a filehandle for the desired object. Although the whole process isn't repeated every time, the stateless nature of NFS means a fair amount of network traffic which is obviously exacerbated by the distance in your scenario.

You could upgrade your NFS server
Create an aditional server to balance out the load
Add more NFS daemons (nfsd) on the server

Monitor it with nfsstat, especially look at the write rates. Other fields to watch are:

badcalls
nullrecv
badlen
retrans
badxid
timeout

A nonzero in any of these fields could mean trouble.

Hope this helps, Paul

Re: NFS

Tim Malnati — Wed, 18 Oct 2000 11:11:39 GMT

The WAN speed is very important. I've seen a 10ms latency going 3000 miles on an ATM line with new equipment, and I've seen a 200ms latency going across town with some older stuff. The distance is not important in of itself. Traffic on your WAN connection can slow these figures down significantly when things get busy. The bottom line is that NFS can be used successfully over a WAN, but requires that some network engineering be performed to make sure you get the performance you are looking for.

Re: NFS

Darren Miller — Wed, 18 Oct 2000 18:26:36 GMT

Part of the problem may be that NFS uses UDP by default, which may lead to premature timeouts and poor performance. Patch #PHNE_20344 was specifically designed to allow the use of NFS over TCP to improve performance over WANs. After installing the patch, look at the release notes in
/usr/share/doc/RelNotesNFS_TCP.txt for more information.

Darren