linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Richard Kennedy <richard@rsk.demon.co.uk>
To: Heinz Diehl <htd@fancy-poultry.org>
Cc: linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
	lwoodman@redhat.com
Subject: Re: RFC: dirty_ratio back to 40%
Date: Thu, 20 May 2010 14:47:55 +0100	[thread overview]
Message-ID: <4BF53D8B.5090407@rsk.demon.co.uk> (raw)
In-Reply-To: <20100520122919.GA3420@fancy-poultry.org>

On 20/05/10 13:29, Heinz Diehl wrote:
> On 20.05.2010, Larry Woodman wrote: 
> lwoodman@redhat.com
>> Increasing the dirty_ratio to 40% will regain the performance loss seen
>> in several benchmarks.  Whats everyone think about this???
> 
> These are tuneable via sysctl. What I have in my /etc/sysctl.conf is
> 
>  vm.dirty_ratio = 4
>  vm.dirty_background_ratio = 2
>  
> This writes back the data more often and frequently, thus preventing the
> system from long stalls. 
> 
> Works at least for me. AMD Quadcore, 8 GB RAM.
> 
get_dirty_limits uses a minimum vm_dirty_ratio of 5, so you can't set it
lower than that (unless you use vm_dirty_bytes).
But it's interesting that you find lowering the dirty_ratio helpful. Do
you have any benchmark results you can share?
regards
Richard

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-05-20 13:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 11:20 Larry Woodman
2010-05-20 12:29 ` Heinz Diehl
2010-05-20 13:47   ` Richard Kennedy [this message]
2010-05-20 23:48 ` KOSAKI Motohiro
2010-05-21  0:48   ` Zan Lynx
2010-05-21  1:11     ` KOSAKI Motohiro
2010-05-21 16:00       ` Jan Kara
2010-05-24 19:50     ` Ric Wheeler
2010-05-21 15:50   ` Jan Kara
2010-05-21  6:18 ` David Miller
2010-06-08 18:49 ` Christoph Hellwig
2010-06-08 19:01   ` Larry Woodman

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=4BF53D8B.5090407@rsk.demon.co.uk \
    --to=richard@rsk.demon.co.uk \
    --cc=htd@fancy-poultry.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lwoodman@redhat.com \
    /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