From: Jehan PROCACCIA <Jehan.Procaccia@int-evry.fr>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Jeff Blaine <jblaine@mitre.org>, nfs@lists.sourceforge.net
Subject: Re: 2.4.21 NFSv3 performance graph
Date: Fri, 21 Jan 2005 18:09:29 +0100 [thread overview]
Message-ID: <41F13749.4090900@int-evry.fr> (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:
>
>
>>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_10533_image001.gif
>>
>>
>
>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).
>
>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.
>
> Trond
>
>
Hello,
more generaly, what tool do you recommand to bench NFS ?
I tried bonnie, bonnie++ and iozone.
for the latest here's the kind of command I ran (so that it doesn't
takes hours to run the test!):
/opt/iozone/bin/iozone -p -s 10k -s 100k -s 1m -s 5m -s 10m -s 100m -i
0 -i 1 -r 4 -r 64 -r 256 -r 512 -r 1024 -r 4096 -r8192 -r 16384 -c -U
/mnt/cobra3 -f /mnt/cobra3/iozone.nagiostux > iozone-result
My problem is that my NFS server has 4Go of ram, and bench programs
always recommand to use filesize for tests higher than RAM size and even
double size of the RAM so that it is not messuring cache activities !
Can you give me a sample of the iozone arguments you used ?
Any other tools ?
thanks.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-01-21 17:09 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
2005-01-18 17:08 ` Vincent Roqueta
2005-01-21 17:09 ` Jehan PROCACCIA [this message]
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=41F13749.4090900@int-evry.fr \
--to=jehan.procaccia@int-evry.fr \
--cc=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.