From: Matthew Mitchell <matthew@geodev.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: mmap() and NFS server performance
Date: Mon, 16 Dec 2002 08:33:57 -0600 [thread overview]
Message-ID: <3DFDE455.1000004@geodev.com> (raw)
In-Reply-To: shsadj826bt.fsf@charged.uio.no
Trond Myklebust wrote:
>>>>>>" " == Matthew Mitchell <matthew@geodev.com> writes:
>>>>>
>
> > values. These apps were originally written on Solaris with
> > Solaris NFS servers assumed to be the data source; the Sun guys
> > said that mmap would be much faster than read/write and they
> > were correct. However, now that we have a few Linux NFS
> > servers, we're seeing the opposite.
>
> As long as the clients are still Solaris, then the only difference can
> be the network, and the server performance.
>
> Of the 2, the bigger 'generic' troublemaker tends to be the network.
> Solaris clients always tend to prefer NFS over TCP since that tends to
> be more reliable on poor networks than does UDP. Unfortunately, NFS
> over TCP on the server side is a fairly recent addition to Linux: it
> only just made it into the stable release 2 weeks ago (when 2.4.20 was
> released). To the best of my knowledge, none of the RedHat kernels
> support it yet.
For some reason it had not occurred to me that the NFS server on the
Linux box might be using UDP instead of TCP; I had it in my head somehow
that it would use TCP. Obviously it wasn't. Now, we had noticed slower
speeds with UDP before (when Linux clients were using UDP to access the
Solaris servers). Could this be causing such a drastic slowdown?
I have looked at some network packet streams and I don't think we are
having any of the classic UDP problems -- negligible # of retransmits,
most packets arrive in order. The Linux server isn't loaded hardly at all.
Three further questions:
1) What would you like to see, tcpdump/snoop wise, to verify this?
2) Could UDP service really be causing this order of magnitude slowdown?
3) Is TCP server code "ready enough" for production use? In our case we
don't mind some occasional bugs, but it needs to be able to stay working
under reasonable load for a day or so at a time for us to get anything
done ("Stale NFS file handle" is a scourge...).
Thanks again.
--
Matthew Mitchell
Systems Programmer/Administrator matthew@geodev.com
Geophysical Development Corporation phone 713 782 1234
1 Riverway Suite 2100, Houston, TX 77056 fax 713 782 1829
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-12-16 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 21:09 mmap() and NFS server performance Matthew Mitchell
2002-12-13 21:35 ` Brian Pawlowski
2002-12-14 11:22 ` Trond Myklebust
2002-12-16 14:33 ` Matthew Mitchell [this message]
2002-12-16 14:50 ` Trond Myklebust
2002-12-16 20:04 ` Matthew Mitchell
2002-12-14 16:51 ` David B. Ritch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DFDE455.1000004@geodev.com \
--to=matthew@geodev.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.