All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Hodgson <matthew@mxtelecom.com>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Tuning NFS client write pagecache
Date: Fri, 06 Aug 2010 17:29:29 +0100	[thread overview]
Message-ID: <4C5C3869.1040900@mxtelecom.com> (raw)
In-Reply-To: <20100806132620.GA2921@merit.edu>

Hi,

Jim Rees wrote:
> Matthew Hodgson wrote:
> 
>   Is there any way to tune the linux NFSv3 client to prefer to write
>   data straight to an async-mounted server, rather than having large
>   writes to a file stack up in the local pagecache before being synced
>   on close()?
> 
> It's been a while since I've done this, but I think you can tune this with
> vm.dirty_writeback_centisecs and vm.dirty_background_ratio sysctls.  The
> data will still go through the page cache but you can reduce the amount
> that
> stacks up.

Yup, that does the trick - I'd tried this earlier, but hadn't gone far 
enough - seemingly I need to drop vm.dirty_writeback_centisecs down to 1 
(and vm.dirty_background_ratio to 1) for the back-pressure to propagate 
correctly for this use case.  Thanks for the pointer!

In other news, whilst saturating the ~10Mb/s pipe during the big write 
to the server, I'm seeing huge delays of >10 seconds on trying to do 
trivial operations such as ls'ing small directories.  Is this normal, or 
is there some kind of tunable scheduling on the client to avoid a single 
big transfer wedging the machine?

thanks,

Matthew

-- 
Matthew Hodgson
Development Program Manager
OpenMarket | www.openmarket.com/europe
matthew.hodgson@openmarket.com

  parent reply	other threads:[~2010-08-06 16:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 12:21 Tuning NFS client write pagecache Matthew Hodgson
2010-08-06 13:26 ` Jim Rees
2010-08-06 14:05   ` Peter Chacko
2010-08-06 17:37     ` Trond Myklebust
2010-08-06 19:29       ` Peter Chacko
2010-08-06 19:39         ` Trond Myklebust
2010-08-07  3:15           ` Peter Chacko
2010-08-10 16:27             ` Chuck Lever
2010-08-10 17:52               ` Peter Chacko
2010-08-10 18:19                 ` David Brodbeck
2010-08-10 19:16                 ` Chuck Lever
2010-08-10 20:50               ` Gilliam, PaulX J
2010-08-10 21:47                 ` Chuck Lever
2010-08-11  2:09                   ` Peter Chacko
2010-08-11 16:05                     ` Chuck Lever
2010-08-11 17:14                       ` Peter Chacko
2010-08-11 20:51                         ` Chuck Lever
2010-08-06 16:29   ` Matthew Hodgson [this message]
2010-08-07  0:25     ` Matthew Hodgson

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=4C5C3869.1040900@mxtelecom.com \
    --to=matthew@mxtelecom.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.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.