From: Steven Pratt <slpratt@austin.ibm.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: experimental branch rebased
Date: Thu, 26 Feb 2009 16:54:13 -0600 [thread overview]
Message-ID: <49A71D95.8030707@austin.ibm.com> (raw)
In-Reply-To: <1235663145.4631.11.camel@think.oraclecorp.com>
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).
Also, I have reordered the bars with btrfs at the end for 2 reasons.
First, makes it a little easier to find the latest btrfs results. Also
this fixes a problem with my scripts where I was not picking up the
random write odirect tests.
Single disk tests are running.
Steve
> -chris
>
>
next prev parent reply other threads:[~2009-02-26 22:54 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 [this message]
2009-02-27 16:25 ` Chris Mason
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=49A71D95.8030707@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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