linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sonny Rao <sonny@burdell.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	ext2-devel <ext2-devel@lists.sourceforge.net>,
	linux-fsdevel@vger.kernel.org, sct@redhat.com
Subject: Re: Re: [RFC] ext3 writepages for writeback mode
Date: Mon, 14 Feb 2005 15:02:56 -0500	[thread overview]
Message-ID: <20050214200256.GA3690@kevlar.burdell.org> (raw)
In-Reply-To: <1108166986.20053.1235.camel@dyn318077bld.beaverton.ibm.com>

On Fri, Feb 11, 2005 at 04:09:46PM -0800, Badari Pulavarty wrote:
> On Fri, 2005-02-11 at 15:58, Andrew Morton wrote:
> > Badari Pulavarty <pbadari@us.ibm.com> wrote:
> > >
> > > Due to lack of interesting suggestions to solve 
> > > mpage_writepages() -> ext3_writeback_writepage() problem,
> > > I fixed it in the dumbest possible way.
> > 
> > I've actually forgotten what the problem was.  It was 100 patches ago :(
> 
> The problem was 
> 	ext3_writeback_writepages() -> mpage_writepages() could
> call back ext3_writeback_writepage() in the "confused" case.
> ext3_writeback_writepage() could end up doing nothing, since the
> we already have a journal handle.
> 
> I added a writepage_helper to handle this case.
> 
> > 
> > > Let me know, what you think.
> > 
> > 
> > If it works, let's get some benchmark numbers so we can decide whether it
> > justifies more development?
> > 
> 
> Yep. I will get some numbers to see ..
> 

I'm helping Badari collecting data on this...

My setup is a P4 2.0Ghz booted with 1GB of RAM and 1 cpu attached via
Fiber to a seven disk raid0 array with write-caching turned off
(write-cacheing can skew numbers significantly if you aren't careful
to let the cache drain between runs, etc.) 

The test is a single-threaded sequential overwrite of a 20GB data set
divided into 512MB files which are selected randomly and overwritten.

All of these numbers represent the average of three five-minute runs.

All ext3 tests are in writeback mode

FS		Throughput	Cpu Utilizaiton
--		----------	---------------
Ext3		78 MB/sec	75.9 %
Ext3 + wpages	85 MB/sec	74.7 %

Just for comparison:

Ext2		88.5 MB/sec	74.2 %
Ext2 + nobh	89.6 MB/sec	71.7 %

JFS		94.8 MB/sec	85.6 %
XFS		100 MB/sec	95.5 %


So, Badari's writepages patch improves performance on this particular
setup by almost 10 %


I can rerun with more processors/ram, or different disk configurations
if anyone is interested.

Sonny


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-14 20:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11  1:31 [RFC] ext3 writepages for writeback mode Badari Pulavarty
2005-02-11  1:53 ` Andrew Morton
2005-02-11  3:06   ` Badari Pulavarty
2005-02-11 23:29   ` Badari Pulavarty
2005-02-11 23:58     ` Andrew Morton
2005-02-12  0:09       ` Badari Pulavarty
2005-02-14 20:02         ` Sonny Rao [this message]
2005-02-14 20:22           ` [Ext2-devel] " Sonny Rao
2005-02-12  0:51       ` Badari Pulavarty
2005-02-12  1:00         ` Andrew Morton
2005-02-12  1:55           ` Badari Pulavarty
2005-02-12 12:20         ` [Ext2-devel] " Alex Tomas
2005-02-12 18:47           ` Badari Pulavarty
2005-02-12 21:43             ` Alex Tomas
2005-02-12 23:26           ` Badari Pulavarty
2005-02-12 23:29             ` Alex Tomas
2005-02-14 15:58               ` Badari Pulavarty
2005-02-14 16:34                 ` Alex Tomas
2005-02-14 16:50 ` Thiago Rondon
2005-02-14 18:08   ` Badari Pulavarty

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=20050214200256.GA3690@kevlar.burdell.org \
    --to=sonny@burdell.org \
    --cc=akpm@osdl.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=sct@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;
as well as URLs for NNTP newsgroup(s).