From: Ric Wheeler <rwheeler@redhat.com>
To: Zan Lynx <zlynx@acm.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
lwoodman@redhat.com, LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Nick Piggin <npiggin@suse.de>,
Jan Kara <jack@suse.cz>
Subject: Re: RFC: dirty_ratio back to 40%
Date: Mon, 24 May 2010 15:50:49 -0400 [thread overview]
Message-ID: <4BFAD899.4020909@redhat.com> (raw)
In-Reply-To: <4BF5D875.3030900@acm.org>
On 05/20/2010 08:48 PM, Zan Lynx wrote:
> On 5/20/10 5:48 PM, KOSAKI Motohiro wrote:
>> Hi
>>
>> CC to Nick and Jan
>>
>>> We've seen multiple performance regressions linked to the lower(20%)
>>> dirty_ratio. When performing enough IO to overwhelm the background
>>> flush daemons the percent of dirty pagecache memory quickly climbs
>>> to the new/lower dirty_ratio value of 20%. At that point all writing
>>> processes are forced to stop and write dirty pagecache pages back to
>>> disk.
>>> This causes performance regressions in several benchmarks as well as
>>> causing
>>> a noticeable overall sluggishness. We all know that the dirty_ratio is
>>> an integrity vs performance trade-off but the file system journaling
>>> will cover any devastating effects in the event of a system crash.
>>>
>>> Increasing the dirty_ratio to 40% will regain the performance loss seen
>>> in several benchmarks. Whats everyone think about this???
>>
>> In past, Jan Kara also claim the exactly same thing.
>>
>> Subject: [LSF/VM TOPIC] Dynamic sizing of dirty_limit
>> Date: Wed, 24 Feb 2010 15:34:42 +0100
>>
>> > (*) We ended up increasing dirty_limit in SLES 11 to 40% as it
>> used to be
>> > with old kernels because customers running e.g. LDAP (using BerkelyDB
>> > heavily) were complaining about performance problems.
>>
>> So, I'd prefer to restore the default rather than both Redhat and
>> SUSE apply exactly
>> same distro specific patch. because we can easily imazine other users
>> will face the same
>> issue in the future.
>
> On desktop systems the low dirty limits help maintain interactive
> feel. Users expect applications that are saving data to be slow. They
> do not like it when every application in the system randomly comes to
> a halt because of one program stuffing data up to the dirty limit.
>
> The cause and effect for the system slowdown is clear when the dirty
> limit is low. "I saved data and now the system is slow until it is
> done." When the dirty page ratio is very high, the cause and effect is
> disconnected. "I was just web surfing and the system came to a halt."
>
> I think we should expect server admins to do more tuning than desktop
> users, so the default limits should stay low in my opinion.
>
Have you done any performance testing that shows this?
A laptop the smaller default would spin up drives more often and greatly
decrease your battery life.
Note that both SLES and RHEL default away from the upstream default.
Ric
--
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-24 19:51 UTC|newest]
Thread overview: 12+ 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 12:29 ` Heinz Diehl
2010-05-20 13:47 ` Richard Kennedy
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 [this message]
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=4BFAD899.4020909@redhat.com \
--to=rwheeler@redhat.com \
--cc=jack@suse.cz \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=npiggin@suse.de \
--cc=zlynx@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).