From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: experimental branch rebased
Date: Fri, 27 Feb 2009 11:25:32 -0500 [thread overview]
Message-ID: <1235751932.12383.11.camel@think.oraclecorp.com> (raw)
In-Reply-To: <49A71D95.8030707@austin.ibm.com>
On Thu, 2009-02-26 at 16:54 -0600, Steven Pratt wrote:
> Chris Mason wrote:
> > Hello everyone,
> >
> > I've rebased the experimental branch again with my latest performance
> > fixes.
> >
> > I took out the delayed unlink code, it wasn't making a big enough
> > difference in any benchmarks to justify the complexity.
> >
> > I changed the delayed backref code to do delayed processing for all
> > extents. In general it is much faster and uses less stack.
> >
> > I pulled Josef's enospc work into the master branch and asked Linus to
> > pull it.
> >
> > I'm going to hammer on the experimental branch for a few days and ask
> > Steve to give it another run.
> >
> Done. Results for RAID are updated in history tree
> http://btrfs.boxacle.net/repository/raid/history/History.html
>
> This gives back a few of the performance improvements made on the tree
> from the 24th (mail server and random write).
>
Thanks for doing this. I'm a little confused by the output though,
somehow our configs are giving opposite results ;)
When I run the rand-write workload with 128 threads here, btrfs gets
6236 ops/sec, and ext4 only gets 1509 ops/sec.
My box only has 5 drives, so there is probably a difference in btrfs'
ability to keep all the drives in the array busy.
So, I'll do some more experiments here.
-chris
prev parent reply other threads:[~2009-02-27 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 15:45 experimental branch rebased Chris Mason
2009-02-26 19:05 ` Lee Trager
2009-03-03 22:07 ` jim owens
2009-03-07 4:53 ` Lee Trager
2009-03-09 13:26 ` jim owens
2009-02-26 22:54 ` Steven Pratt
2009-02-27 16:25 ` Chris Mason [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=1235751932.12383.11.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.ibm.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