From: Jim Rees <rees@umich.edu>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Judith Flo Gaya <jflo@imppc.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: problem with nfs latency during high IO
Date: Wed, 16 Mar 2011 11:18:28 -0400 [thread overview]
Message-ID: <20110316151827.GA12187@merit.edu> (raw)
In-Reply-To: <E6EAC031-956D-42E7-AF01-72AD36474E8B@oracle.com>
Chuck Lever wrote:
> I was wondering what is the minimum number that it is safe to use? I'm
sure that you have already dealt with the side-effects/collateral
damages of this action, I don't want to fix a problem creating another
one..
As I said before, you can set it to 1, and that will mean background
flushing kicks in at 1% of your client's physical memory.
I think 5 is the minimum for dirty_ratio, although this doesn't seem to be
documented anywhere. If you want to set it lower, you have to use
dirty_bytes instead of dirty_ratio. See the commit message here:
http://lkml.org/lkml/2008/11/23/160
Documentation is in Documentation/sysctl/vm.txt.
next prev parent reply other threads:[~2011-03-16 15:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 12:58 problem with nfs latency during high IO Judith Flo Gaya
2011-03-15 16:24 ` Chuck Lever
2011-03-15 17:25 ` Judith Flo Gaya
2011-03-15 18:03 ` Chuck Lever
2011-03-15 18:15 ` Chuck Lever
2011-03-17 1:21 ` Harshula Jayasuriya
2011-03-15 21:33 ` Judith Flo Gaya
2011-03-15 21:28 ` Chuck Lever
2011-03-15 21:58 ` Judith Flo Gaya
2011-03-15 22:10 ` Chuck Lever
2011-03-16 11:45 ` Judith Flo Gaya
2011-03-16 13:24 ` Chuck Lever
2011-03-16 13:42 ` peter.staubach
2011-03-16 15:18 ` Jim Rees [this message]
2011-03-16 15:31 ` Jim Rees
2011-03-16 16:52 ` Judith Flo Gaya
2011-03-16 23:51 ` Simon Kirby
-- strict thread matches above, loose matches on Subject: below --
2011-03-15 16:25 Judith Flo Gaya
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=20110316151827.GA12187@merit.edu \
--to=rees@umich.edu \
--cc=chuck.lever@oracle.com \
--cc=jflo@imppc.org \
--cc=linux-nfs@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 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.