From: Wil Reichert <wil.reichert@gmail.com>
To: Mike Ramsey <MikeJRamsey@comcast.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Phoronix article slaming BTRFS
Date: Tue, 23 Jun 2009 19:20:50 -0700 [thread overview]
Message-ID: <7a329d910906231920l49236acer404369643a2cf833@mail.gmail.com> (raw)
In-Reply-To: <loom.20090624T011230-219@post.gmane.org>
On Tue, Jun 23, 2009 at 6:27 PM, Mike Ramsey<MikeJRamsey@comcast.net> w=
rote:
> Jaime sanchez <jskartman <at> gmail.com> writes:
>
>>
>> They are using 2.6.29.4 kernel, it isn't a bit old??
>>
>> =C2=A0I think that kernel doesn't have the last btrfs updates, and t=
hat it
>> =C2=A0is a very bad work and benchmarks results from phoronix part. =
If u are
>> =C2=A0benchmarking an experimental file system benchmark it with the=
latest
>> =C2=A0updates =C2=BF? it doesn't have sense.
> [snip]
>
> I agree. =C2=A0It was either a hatchet job or just a poor effort. =C2=
=A0The problem is
> that a lot of people are going to read it and lose interest in btrfs.=
=C2=A0I was
> disheartened but then the analyst in me said, "Wait, this just can't =
be right.
> A copy-on-write file system has got be screaming!"
>
> So I decided to dig deeper.
>
> It might not be a bad idea to get some counter information out there.=
=C2=A0It should
> explicitly reference and refute the phoronix article. =C2=A0Tom's Har=
dware
> http://www.tomshardware.com/
> is a reputable place. =C2=A0They would run a fair benchmark and their=
work would
> carry weight.
>
> BTW, the Sun side of Oracle isn't likely to release ZFS to the Linux =
world
> because they need to preserve a competitive edge for Solaris.
>
> Butters has a future. =C2=A0Believe it.
I seriously doubt Phoronix has anything against btrfs, most likely
quite the opposite. My suggestion is either to show where their
benchmarks are in err, or come up with better benchmarks that
demonstrate btrfs in a more positive light. Its quite possible
Phoronix would post updated benchmarks regarding the topic.
Wil
--
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 2:20 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 [this message]
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=7a329d910906231920l49236acer404369643a2cf833@mail.gmail.com \
--to=wil.reichert@gmail.com \
--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