From: Mingming Cao <cmm@us.ibm.com>
To: Andreas Dilger <adilger@sun.com>
Cc: "Jose R. Santos" <jrs@us.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linux-ext4@vger.kernel.org
Subject: Re: ext4 compile bench is slower
Date: Fri, 25 Jul 2008 17:58:57 -0700 [thread overview]
Message-ID: <1217033937.6394.7.camel@mingming-laptop> (raw)
In-Reply-To: <20080725215901.GA3181@webber.adilger.int>
在 2008-07-25五的 18:00 -0400,Andreas Dilger写道:
> On Jul 23, 2008 08:30 -0500, Jose R. Santos wrote:
> > On Tue, 22 Jul 2008 18:58:50 -0600
> > Andreas Dilger <adilger@sun.com> wrote:
> > > Jose, do you have ext3 results on the same system
> > > for the benchmarks you ran? That would tell us how much improvement we
> > > get from other ext4 features (e.g. extents vs. block allocation) and how
> > > much from flex_bg.
> >
> > No I dont, I tried doing some runs yesterday but after updating the
> > kernel, the results flex_bg are about the same as without it and ext3
> > is a lot faster than ext4. Im investigating to see if I messed up the
> > kernel build somehow or if we have a regression.
>
> There was another report that the current ext4 code is no longer faster
> at compilebench than ext3.
>
> > Valerie did a very comprehensive set of comparisons that could be
> > useful for the presentation. I'll try to see if I can recreate this
> > once I figure out the regression im seeing but would this work for now?
> >
> > http://www.bullopensource.org/ext4/20080530/ffsb-readwrite-2.6.26-rc2.html
>
Between 2.6.26-rc2 to now the biggest change is the locking ordering
change (page lock and transaction) and the new ordered mode, and the
delalloc get updated to adopt the new locking order. I wonder if that's
the cause....
Mingming
> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-07-26 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080709165655.GB29109@skywalker>
[not found] ` <20080709215728.GD6239@webber.adilger.int>
[not found] ` <20080710042453.GA6764@skywalker>
[not found] ` <20080714144442.GA1041@skywalker>
[not found] ` <20080714100153.0f9756e3@ichigo>
[not found] ` <20080721222357.56471dd5@gara>
[not found] ` <20080723005850.GF19325@webber.adilger.int>
[not found] ` <20080723083033.4bdddf08@gara>
2008-07-25 22:00 ` ext4 compile bench is slower Andreas Dilger
2008-07-26 0:58 ` Mingming Cao [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=1217033937.6394.7.camel@mingming-laptop \
--to=cmm@us.ibm.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=jrs@us.ibm.com \
--cc=linux-ext4@vger.kernel.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