From: Jens Axboe <jens.axboe@oracle.com>
To: Mike Ramsey <MikeJRamsey@comcast.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Phoronix article slaming BTRFS
Date: Wed, 24 Jun 2009 19:38:37 +0200 [thread overview]
Message-ID: <20090624173836.GR31415@kernel.dk> (raw)
In-Reply-To: <loom.20090624T130012-322@post.gmane.org>
On Wed, Jun 24 2009, Mike Ramsey wrote:
> Jens Axboe <jens.axboe <at> oracle.com> writes:
>
> >
> > On Wed, Jun 24 2009, Mike Ramsey wrote:
> > > Stephan von Krawczynski <skraw <at> ithnet.com> writes:
> [snip]
> > > Depends on who you talk to.
> > >
> > > http://www.tomshardware.com/news/ocz-ssd-vertex-intel-solid-state,7127.html
> > >
> > > "OCZ Says Its New Vertex SSD Beats Intel's X25-E"
> >
> > Heh, the Vertex beating the X25-E? I think such a statement could only
> > come from OCZ. No amount of magic will suddenly make MLC beat SLC, let
> > alone a well tuned firmware like the X25-E's. I'm sure they concocted
> > some synthetic benchmark where the Vertex has some slight edge. In the
> > real world, the X25-E wipes the floor with the Vertex.
> >
> > The Vertex is indeed a good performer, in its price range it's currently
> > the one to beat. I have doubts about the maturity of the product though,
> > looks mostly like a live beta being tested in the field. So I'd just be
> > careful with what kind of use they are put to. But just running tests on
> > the drive does show that it performs well for most things.
> >
>
> If I was buying for business than the Intel drives would be my choice.
> They are clearly the quality leader. For instance, Intel has tweaked
> their firmware to optimize for small IOs. The X25-E and X25-M are class.
> We agree here I think.
>
> For home use where it is *my* money I am willing to have a little faith
> in order to save a couple hundred dollars. I realize that OCZ and its
> controller supplier will be shipping firmware updates. But don't kid
> yourself, so is Intel.
Of course they do, everything has bugs. What I'm worried about is the
severity of those bugs, and the amount and quality of testing that has
gone into these products.
> BTW, what OCZ did to increase speed was to increase the cache size in
> their large capacity high end Vertex models. This wouldn't help my
> 30 GB model.
It's easy to throw cache at the problem and make it faster. That's like
shaving weight off a car. Might make it go faster, definitely wont make
it safer.
--
Jens Axboe
next prev parent reply other threads:[~2009-06-24 17:38 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
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 [this message]
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=20090624173836.GR31415@kernel.dk \
--to=jens.axboe@oracle.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