From: Larry Woodman <lwoodman@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: RFC: dirty_ratio back to 40%
Date: Tue, 08 Jun 2010 15:01:24 -0400 [thread overview]
Message-ID: <1276023684.8736.51.camel@dhcp-100-19-198.bos.redhat.com> (raw)
In-Reply-To: <20100608184913.GA12154@infradead.org>
On Tue, 2010-06-08 at 14:49 -0400, Christoph Hellwig wrote:
> Did this patch get merged somewhere?
I dont think it ever did, about 1/2 of responses were for it and the
other 1/2 against it.
Larry
>
> On Thu, May 20, 2010 at 07:20:42AM -0400, Larry Woodman wrote:
> > 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???
> >
> >
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> > index ef27e73..645a462 100644
> > --- a/mm/page-writeback.c
> > +++ b/mm/page-writeback.c
> > @@ -78,7 +78,7 @@ int vm_highmem_is_dirtyable;
> > /*
> > * The generator of dirty data starts writeback at this percentage
> > */
> > -int vm_dirty_ratio = 20;
> > +int vm_dirty_ratio = 40;
> >
> > /*
> > * vm_dirty_bytes starts at 0 (disabled) so that it is a function of
> >
> > --
> > 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>
> ---end quoted text---
>
> --
> 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>
--
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>
prev parent reply other threads:[~2010-06-08 18:56 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
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 [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=1276023684.8736.51.camel@dhcp-100-19-198.bos.redhat.com \
--to=lwoodman@redhat.com \
--cc=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox