All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gnb@sgi.com>
To: Bruce Allan <bwa@us.ibm.com>
Cc: nfs@lists.sourceforge.net, okir@suse.de
Subject: Re: nfsd write throughput
Date: Wed, 4 Aug 2004 18:18:21 +1000	[thread overview]
Message-ID: <20040804081821.GQ5581@sgi.com> (raw)
In-Reply-To: <1091578243.4797.52.camel@dyn319492.beaverton.ibm.com>

On Tue, Aug 03, 2004 at 05:10:44PM -0700, Bruce Allan wrote:
> Greg Banks <gnb@sgi.com> wrote on 08/02/2004 07:10:18 PM:
> 
> <snip>
> > First, the way the v3 server is supposed to work is that normal
> > page cache pressure pushes pages from unstable writes to disk
> > before the COMMIT call arrives from the client.  The best way to
> > achieve this for a dedicated NFS server box is tuning the pdflush
> > parameters to be more aggressive about writing back dirty pages,
> > e.g. bumping down the following in /proc/vm:
> > dirty_background_ration, dirty_ratio, dirty_writeback_centisecs,
> > and dirty_expire_centisecs.  I have to admit I've not tried this
> > yet on 2.6 but the equivalent on 2.4 has been generally useful.
> <snip>
> 
> This information (and the comparable info for 2.6) should be in Chapter
> 5. Optimizing NFS Performance of the NFS-HOWTO
> (http://nfs.sourceforge.net/nfs-howto/performance.html).

Yes.

> Greg, can you
> throw together a documentation patch?  If you don't have the time and/or
> inclination, I could give it a shot if you care to review the content. 

That document has several wrong or outdated pieces of advice, e.g. in
sections 5.1, 5.4, 5.7.  If you want me to write a diff it won't be
a trivial one and you'll have to wait while I plow through some of
the other four dozen bugs I have queued up.  I'm happy to do it if
you're happy to wait.

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-08-04  8:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04  0:10 nfsd write throughput Bruce Allan
2004-08-04  8:18 ` Greg Banks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-02 16:24 Olaf Kirch
2004-08-03  2:10 ` Greg Banks
2004-08-03  6:02   ` Olaf Kirch
2004-08-03  7:55     ` Greg Banks
2004-08-03  8:09       ` Olaf Kirch
2004-08-03  8:28         ` Greg Banks
2004-08-03 10:32       ` Olaf Kirch
2004-08-03 10:52         ` Olaf Kirch
2004-08-03 11:24         ` Greg Banks
2004-08-03 13:26           ` Olaf Kirch
2004-08-03  2:23 ` Neil Brown

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=20040804081821.GQ5581@sgi.com \
    --to=gnb@sgi.com \
    --cc=bwa@us.ibm.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=okir@suse.de \
    /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.