From: Mike Ramsey <MikeJRamsey@comcast.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Phoronix article slaming BTRFS
Date: Wed, 24 Jun 2009 01:27:06 +0000 (UTC) [thread overview]
Message-ID: <loom.20090624T011230-219@post.gmane.org> (raw)
In-Reply-To: 2d23818a0906231028t43d97e64t901610ca18e749d0@mail.gmail.com
Jaime sanchez <jskartman <at> gmail.com> writes:
>=20
> They are using 2.6.29.4 kernel, it isn't a bit old??
>=20
> I think that kernel doesn't have the last btrfs updates, and that it
> is a very bad work and benchmarks results from phoronix part. If u a=
re
> benchmarking an experimental file system benchmark it with the lates=
t
> updates =C2=BF? it doesn't have sense.
[snip]=20
I agree. It was either a hatchet job or just a poor effort. The probl=
em is
that a lot of people are going to read it and lose interest in btrfs. =
I was
disheartened but then the analyst in me said, "Wait, this just can't be=
right.=20
A copy-on-write file system has got be screaming!" =20
So I decided to dig deeper. =20
It might not be a bad idea to get some counter information out there. =
It should
explicitly reference and refute the phoronix article. Tom's Hardware
http://www.tomshardware.com/
is a reputable place. They would run a fair benchmark and their work w=
ould
carry weight.
BTW, the Sun side of Oracle isn't likely to release ZFS to the Linux wo=
rld
because they need to preserve a competitive edge for Solaris. =20
Butters has a future. Believe it.
--Mike Ramsey
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-24 1:27 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 [this message]
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
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=loom.20090624T011230-219@post.gmane.org \
--to=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