From: Chris Penney <cpenney@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS tuning - high performance throughput.
Date: Wed, 15 Jun 2005 16:33:08 -0400 [thread overview]
Message-ID: <111aefd0506151333415a4655@mail.gmail.com> (raw)
In-Reply-To: <1118866263.22484.21.camel@seki.nac.uci.edu>
On 6/15/05, Dan Stromberg <strombrg@dcs.nac.uci.edu> wrote:
> On Wed, 2005-06-15 at 14:52 -0500, Roger Heflin wrote:
> > The mount/remount (unless you time how long it takes to unmount),
> > will potentially still skew the write test, and the writes
> > will still be happening for quite a while after the dd completes.
>=20
> Or unless you sync twice? Or write synchronously.
>=20
You can optionally use iozone (www.iozone.org) you can use '-c -e' to
include fsync() and close() times. It also has an option to umount
the volume between iterations.
Also, I missed that he was using a 4k stripe size before. That's got
to be his issue. My luns are 8+1 h/w raid 5 using a 64k segment size
per disk and I use 512k (8*64) as the stripe size. As was
intelligently noted, you really want your writes to fill a whole
stripe if you can. If they do not my understanding is that you should
lower both your segment size and stripe width. I think you always
want your stripe width to match the width of your raid 5 lun.
Chris
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-06-15 20:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050610031144.4B9CA12F8C@sc8-sf-spam2.sourceforge.net>
2005-06-14 20:17 ` NFS tuning - high performance throughput M. Todd Smith
2005-06-14 20:41 ` Bill Rugolsky Jr.
2005-06-14 22:49 ` M. Todd Smith
2005-06-15 13:03 ` Roger Heflin
2005-06-15 14:47 ` M. Todd Smith
2005-06-15 15:28 ` Roger Heflin
2005-06-15 19:13 ` Dan Stromberg
2005-06-15 19:52 ` Roger Heflin
2005-06-15 20:11 ` Dan Stromberg
2005-06-15 20:31 ` Roger Heflin
2005-06-15 20:33 ` Chris Penney [this message]
2005-06-15 17:47 ` Bill Rugolsky Jr.
2005-06-15 20:33 ` M. Todd Smith
2005-06-15 22:43 ` Bill Rugolsky Jr.
2005-06-15 22:47 ` Greg Banks
2005-06-14 20:50 ` Bill Rugolsky Jr.
2005-06-14 21:04 ` Chris Penney
2005-06-14 21:06 ` Chris Penney
2005-06-14 21:11 ` Roger Heflin
[not found] <482A3FA0050D21419C269D13989C611308539C89@lavender-fe.eng.netapp.com>
2005-06-14 20:38 ` M. Todd Smith
2005-06-15 1:56 ` Dan Stromberg
2005-06-14 20:40 Lever, Charles
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=111aefd0506151333415a4655@mail.gmail.com \
--to=cpenney@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=penney@msu.edu \
/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.