From: Heinz Diehl <htd@fancy-poultry.org>
To: linux-kernel@vger.kernel.org
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: RFC: dirty_ratio back to 40%
Date: Thu, 20 May 2010 14:29:19 +0200 [thread overview]
Message-ID: <20100520122919.GA3420@fancy-poultry.org> (raw)
In-Reply-To: <4BF51B0A.1050901@redhat.com>
On 20.05.2010, Larry Woodman wrote:
> 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.
WARNING: multiple messages have this Message-ID (diff)
From: Heinz Diehl <htd@fancy-poultry.org>
To: linux-kernel@vger.kernel.org
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: RFC: dirty_ratio back to 40%
Date: Thu, 20 May 2010 14:29:19 +0200 [thread overview]
Message-ID: <20100520122919.GA3420@fancy-poultry.org> (raw)
In-Reply-To: <4BF51B0A.1050901@redhat.com>
On 20.05.2010, Larry Woodman wrote:
> 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.
--
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>
next prev parent reply other threads:[~2010-05-20 12:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 11:20 RFC: dirty_ratio back to 40% Larry Woodman
2010-05-20 11:20 ` Larry Woodman
2010-05-20 12:29 ` Heinz Diehl [this message]
2010-05-20 12:29 ` Heinz Diehl
2010-05-20 13:47 ` Richard Kennedy
2010-05-20 13:47 ` Richard Kennedy
2010-05-20 17:12 ` Heinz Diehl
2010-05-20 23:48 ` KOSAKI Motohiro
2010-05-20 23:48 ` KOSAKI Motohiro
2010-05-21 0:48 ` Zan Lynx
2010-05-21 0:48 ` Zan Lynx
2010-05-21 1:11 ` KOSAKI Motohiro
2010-05-21 1:11 ` KOSAKI Motohiro
2010-05-21 16:00 ` Jan Kara
2010-05-21 16:00 ` Jan Kara
2010-05-24 19:50 ` Ric Wheeler
2010-05-24 19:50 ` Ric Wheeler
2010-05-21 15:50 ` Jan Kara
2010-05-21 15:50 ` Jan Kara
2010-05-21 6:18 ` David Miller
2010-05-21 6:18 ` David Miller
2010-06-08 18:49 ` Christoph Hellwig
2010-06-08 18:49 ` Christoph Hellwig
2010-06-08 19:01 ` Larry Woodman
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=20100520122919.GA3420@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.