All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Blaine <jblaine@mitre.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: 2.4.21 NFSv3 performance graph
Date: Tue, 18 Jan 2005 09:54:55 -0500	[thread overview]
Message-ID: <41ED233F.2070500@mitre.org> (raw)
In-Reply-To: <1105747170.28849.22.camel@lade.trondhjem.org>

Trond Myklebust wrote:
> fr den 14.01.2005 Klokka 14:00 (-0500) skreiv Jeff Blaine:
>=20
>>Can anyone tell me what is happening in the graph at the URL
>>below?  I can replicate it on any Linux box running 2.4.21
>>and changing rsize/wsize doesn't affect it at all.  This
>>was captured from a 2.6GHz P4 client machine.  Same thing
>>is visible with a Dual 3GHz Xeon box with 4GB memory as a
>>client.  A Solaris 9 client does not display this "falling
>>on face" behavior.
>>
>>http://www.kickflop.net/temp/sol9-server-linux2421-client-gigE-ag930m_1=
0533_image001.gif
>=20
> Firstly, you should always use the '-c' flag when measuring NFS client
> performance. Otherwise, you are basically just measuring the speed with
> which your machine can write to the local page cache (which may indeed
> explain your "knee" at 1MB here - that would be where the client starts
> to force a flush to disk).

Firstly,

Iozone manual:

     "If you use a file size that is larger than the amount of
      memory in the client then the =91c=92 flag is not needed."

I used a file size that is larger than the amount of memory in
the client.

> Secondly, have you actually read the NFS FAQ and NFS HOWTO entries on
> how to tune for performance? Particularly the entries on TCP vs. UDP,
> and how Solaris clients default to the former.

Secondly,

Yes, I have *actually* read the NFS FAQ and NFS HOWTO entries
on how to tune for performance.

It was a pretty simple question.  I don't know what all the
attitude is about.  Do you have an answer you can share with
me or not?

Anyone else?



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-01-18 14:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 19:00 2.4.21 NFSv3 performance graph Jeff Blaine
2005-01-14 23:59 ` Trond Myklebust
2005-01-18 14:54   ` Jeff Blaine [this message]
2005-01-18 17:08     ` Vincent Roqueta
2005-01-21 17:09   ` Jehan PROCACCIA
2005-01-21 17:45     ` Trond Myklebust
2005-01-29 10:48       ` jehan.procaccia
2005-01-29 17:25         ` Iozone
2005-01-30 11:33           ` jehan.procaccia
2005-02-17 13:54             ` jehan.procaccia
2005-02-17 15:44               ` Iozone
2005-02-17 17:27                 ` jehan.procaccia
2005-02-17 17:57                   ` Iozone
2005-02-17 16:00               ` J. Bruce Fields
2005-01-29 17:31         ` Iozone

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=41ED233F.2070500@mitre.org \
    --to=jblaine@mitre.org \
    --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.