All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bron Gondwana <brong@fastmail.fm>
To: Mike Ramsey <MikeJRamsey@comcast.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Phoronix article slaming BTRFS
Date: Thu, 25 Jun 2009 11:32:56 +1000	[thread overview]
Message-ID: <20090625013256.GA6371@brong.net> (raw)
In-Reply-To: <loom.20090624T124800-384@post.gmane.org>

On Wed, Jun 24, 2009 at 12:57:40PM +0000, Mike Ramsey wrote:
> Bron Gondwana <brong <at> fastmail.fm> writes:
> > Meaning that nobody can turn off the write cache in linux without deep kernel
> > hackery.
> 
> I would say this differently.  "Meaning that nobody can turn off the write cache
> in linux without applying the known fixes to libata."

Depending on the environment you're in, building a non-default kernel
can be tricky.

> > 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.
> 
> Real world is running kernel software that is compatible with the unit under
> test.  Benchmarking Butters with a broken kernel is not real world; it's unfair.

Well, yeah.  The world's full of unfair stuff.  I would find this valuable
information to have if I had a kernel of that vintage.
 
> > 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.
> 
> Butters is experimental. Currently, it should only be used under adult
> supervision.  I am looking forward to the day that Butters can be used by
> novices when they click http://www.ubuntu.com/products/GetUbuntu/download

Yeah, that would be nice.  I still use reiser3 in locations where I need a
good all-round filesystem.

Bron ( who probably should get a current kernel again - but the .30rcs were
       causing fun and games with my soundcard and I didn't have time to go
       debuggerising them )

  reply	other threads:[~2009-06-25  1:32 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
2009-06-24 12:57               ` Mike Ramsey
2009-06-25  1:32                 ` Bron Gondwana [this message]
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=20090625013256.GA6371@brong.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.