From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Matthew Mitchell <matthew@geodev.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: mmap() and NFS server performance
Date: 14 Dec 2002 12:22:30 +0100 [thread overview]
Message-ID: <shsadj826bt.fsf@charged.uio.no> (raw)
In-Reply-To: <3DFA4C9A.50101@geodev.com>
>>>>> " " == 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.
Cheers,
Trond
-------------------------------------------------------
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-14 11:22 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 [this message]
2002-12-16 14:33 ` Matthew Mitchell
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=shsadj826bt.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=matthew@geodev.com \
--cc=nfs@lists.sourceforge.net \
/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.