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: Sat, 07 Aug 2010 01:25:46 +0100 [thread overview]
Message-ID: <4C5CA80A.7010501@mxtelecom.com> (raw)
In-Reply-To: <4C5C3869.1040900@mxtelecom.com>
On 06/08/2010 17:29, Matthew Hodgson 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()?
>
> 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?
Hm, on reading the archives, it seems that this is a fairly common
complaint when dealing with large sequential workloads - a sideeffect of
the write pagecache not writing out smoothly.
What is the status of the '[PATCH] improve the performance of large
sequential write NFS workloads' patchset at
http://www.spinics.net/lists/linux-nfs/msg11131.html? It seems that it,
and its predecessors, are intended to fix precisely this issue. It
doesn't seem to have landed in mainline, though, and I can't find any
mention of it since http://lwn.net/Articles/373868/.
thanks,
Matthew
--
Matthew Hodgson
Development Program Manager
OpenMarket | www.openmarket.com/europe
matthew.hodgson@openmarket.com
prev parent reply other threads:[~2010-08-07 0:25 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
2010-08-07 0:25 ` Matthew Hodgson [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=4C5CA80A.7010501@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.