public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Ramsey <MikeJRamsey@comcast.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Phoronix article slaming BTRFS
Date: Wed, 24 Jun 2009 02:47:32 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090624T022909-701@post.gmane.org> (raw)
In-Reply-To: 7a329d910906231920l49236acer404369643a2cf833@mail.gmail.com

Wil Reichert <wil.reichert <at> gmail.com> writes:

> 
> On Tue, Jun 23, 2009 at 6:27 PM, Mike Ramsey<MikeJRamsey <at> 
> comcast.net> wrote:
> > Jaime sanchez <jskartman <at> gmail.com> writes:
> >
> >>
[snip]
> 
> I seriously doubt Phoronix has anything against btrfs, most likely
> quite the opposite.  

I gave two possibilities, 

1. Hatchet job i.e. malice with forethought
2. Just a poor effort

I am not necessary favoring option 1.  Regarding option 2, to err 
is human.

Just admit it, correct it, and then don't repeat it.

> 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

> or come up with better benchmarks that
> demonstrate btrfs in a more positive light.  

That is the ticket.  I suggest that someone contact Tom's Hardware
http://www.tomshardware.com/

And arrange to work with them to perform an honest benchmark.  
Head to head with Ext4 would work for me.  :-)

> Its quite possible
> Phoronix would post updated benchmarks regarding the topic.

They should either repeat the benchmark and do it right, or print a r
etraction.

BTW, thank you for your reply.  I hope that none of the above sounded 
too harsh. The article was IMO damaging and needs to be countered.

--Mike Ramsey
 
[snip]





  reply	other threads:[~2009-06-24  2:47 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 [this message]
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.20090624T022909-701@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