From: Erik Mouw <erik@harddisk-recovery.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Dave Pitts <dpitts@cozx.com>, linux-kernel@vger.kernel.org
Subject: Re: How can I boost block I/O performance
Date: Mon, 8 May 2006 13:18:27 +0200 [thread overview]
Message-ID: <20060508111827.GB1875@harddisk-recovery.com> (raw)
In-Reply-To: <9a8748490605061655oaa7e114ua5dbf47206d92fd6@mail.gmail.com>
On Sun, May 07, 2006 at 01:55:12AM +0200, Jesper Juhl wrote:
> On 5/6/06, Dave Pitts <dpitts@cozx.com> wrote:
> >Hello all:
> >
> >I've been trying some hacks to boost disk I/O performance
> [snip]
> >
> >This test is running several NFS clients to a RAID disk storage array. I
> [snip]
>
> For improving performance of NFS servers I've often had good success
> with increasing the 'rsize' and 'wsize' options.
> The default values are 4096, I personally set them to 16384 which
> usually helps NFS performance quite a bit. At least that's my
> experience.
> Simply add rsize=16384,wsize=16384 to the nfs mount options in
> /etc/fstab and see if that improves performance for you (values like
> 8192 and 32768 may also be worth testing, but personally I've found -
> at least with my setups - that 16384 seems to be the magic value).
> ('man 8 mount' and 'man 5 exports' also have more interresting options
> you may want to experiment with, but just rsize & wsize on their own
> should be a boost)
Another way is to increase the number of nfsd threads on the server.
See rpc.nfsd(8). I usually increase it from the default 8 to 32 on busy
machines.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
prev parent reply other threads:[~2006-05-08 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 18:11 Dave Pitts
2006-05-06 19:31 ` Jon Smirl
2006-05-06 19:35 ` Avi Kivity
2006-05-06 19:32 ` Avi Kivity
2006-05-06 21:17 ` Dave Pitts
2006-05-07 5:13 ` Avi Kivity
2006-05-08 15:41 ` Dave Pitts
2006-05-08 15:50 ` Avi Kivity
2006-05-06 23:55 ` Jesper Juhl
2006-05-08 11:18 ` Erik Mouw [this message]
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=20060508111827.GB1875@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=dpitts@cozx.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®