From: "Bron Gondwana" <brong@fastmail.fm>
To: "Mike Ramsey" <MikeJRamsey@comcast.net>, linux-btrfs@vger.kernel.org
Subject: Re: Phoronix article slaming BTRFS
Date: Wed, 24 Jun 2009 05:31:34 -0400 [thread overview]
Message-ID: <1245835894.6366.1321909165@webmail.messagingengine.com> (raw)
In-Reply-To: <loom.20090624T022909-701@post.gmane.org>
On Tue, 23 Jun 2009 22:47 +0000, "Mike Ramsey" <MikeJRamsey@comcast.net> wrote:
> Wil Reichert <wil.reichert <at> gmail.com> writes:
> > My suggestion is either to show where their
> > benchmarks are in err,
>
> I did this, didn't I?
> 1. Vertex with write cache enabled; disabled would have seen a
> 2X improvement.
> 2. Error in libata
Meaning that nobody can turn off the write cache in linux without deep kernel hackery.
Sounds to me like they are benchmarking the real world rather than trying to favour btrfs by making changes that are unlikely to be viable for anyone trying to run it in production. I.e. they're benchmarking reality.
Sure there are ways that btrfs performance could be improved, but they're not realistically available to mortals selecting "use btrfs for /home" in their Ubuntu "Bleeding-Edge Badger" release.
Bron.
--
Bron Gondwana
brong@fastmail.fm
next prev parent reply other threads:[~2009-06-24 9:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 2:51 Phoronix article slaming BTRFS Mike Ramsey
2009-06-23 10:13 ` Miguel F Mascarenhas Sousa Filipe
[not found] ` <2d23818a0906231026g6e4567fdv8eda3d6c4828ef4d@mail.gmail.com>
2009-06-23 17:28 ` Jaime sanchez
2009-06-24 1:27 ` Mike Ramsey
2009-06-24 2:20 ` Wil Reichert
2009-06-24 2:47 ` Mike Ramsey
2009-06-24 9:31 ` Bron Gondwana [this message]
2009-06-24 12:57 ` Mike Ramsey
2009-06-25 1:32 ` Bron Gondwana
2009-06-23 14:41 ` Chris Mason
2009-06-23 14:53 ` Sander
2009-06-23 15:17 ` Chris Mason
2009-06-23 16:19 ` Stephan von Krawczynski
2009-06-23 16:30 ` Chris Mason
2009-06-24 2:20 ` Mike Ramsey
2009-06-24 8:20 ` Sander
2009-06-24 8:31 ` Jens Axboe
2009-06-24 13:11 ` Mike Ramsey
2009-06-24 17:38 ` Jens Axboe
2009-06-25 8:43 ` Stephan von Krawczynski
2009-06-23 17:30 ` Jaime sanchez
2009-06-23 17:44 ` nightrow
2009-06-23 18:27 ` Jaime sanchez
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=1245835894.6366.1321909165@webmail.messagingengine.com \
--to=brong@fastmail.fm \
--cc=MikeJRamsey@comcast.net \
--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