Linux NFS development
 help / color / mirror / Atom feed
From: Matthew Mitchell <matthew@geodev.com>
To: trond.myklebust@fys.uio.no
Cc: nfs@lists.sourceforge.net
Subject: Re: mmap() and NFS server performance
Date: Mon, 16 Dec 2002 14:04:01 -0600	[thread overview]
Message-ID: <3DFE31B1.40306@geodev.com> (raw)
In-Reply-To: 15869.59466.167433.194706@charged.uio.no

Trond Myklebust wrote:
>>>>>>" " == Matthew Mitchell <matthew@geodev.com> writes:
>>>>>
> 
>      > 1) What would you like to see, tcpdump/snoop wise, to verify
>      >    this?
> 
> nfsstat on the client should normally tell you how often you are
> seeing RPC retransmits.

Ran the program again.  In 20 minutes, around 20k total client RPC 
requests, with an assortment of retrans, time, and badxid errors.  I am 
starting to believe that there is a problem using UDP, and that it alone 
might be enough to explain the slowness.   It seems to have negotiated 
an 8k transfer size.  Reasonable?

>      > 2) Could UDP service really be causing this order of magnitude
>      >    slowdown?
> 
> Certainly: retransmissions follow an *exponential* backoff rule. For
> that reason, it doesn't take a very high percentage of retransmissions
> before you see a large impact.

Seems to be borne out by the evidence.

>      > 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...).
> 
> That is more of a question for Neil Brown, but I personally don't have
> any particularly bad experiences to report.

Any particularly *good* ones? :)  Would you recommend the 2.4.20 set, or 
some additional patches?  I will probably install the new kernel when we 
get a little downtime later this week (and then I will promptly go on 
vacation; hope it stays up! ha!).

Thanks for the suggestions and assistance.  I'll report back with TCP 
info for anyone who is interested.

-- 
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

  reply	other threads:[~2002-12-16 20:08 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
2002-12-16 14:50     ` Trond Myklebust
2002-12-16 20:04       ` Matthew Mitchell [this message]
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=3DFE31B1.40306@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox