public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Miguel F Mascarenhas Sousa Filipe <miguel.filipe@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 11:13:12 +0100	[thread overview]
Message-ID: <f058a9c30906230313v10d94a5eg8cf123cef30fb5b8@mail.gmail.com> (raw)
In-Reply-To: <loom.20090623T024010-331@post.gmane.org>

On Tue, Jun 23, 2009 at 3:51 AM, Mike Ramsey<MikeJRamsey@comcast.net> w=
rote:
> I ran across this article "Testing Out The SSD Mode In Btrfs".
> http://www.phoronix.com/scan.php?page=3Darticle&item=3Dbtrfs_ssd_mode=
&num=3D1
>
> At first I was disappointed. =C2=A0It gave a very disappointing set o=
f benchmarks.
> However, a close reading revealed this:
>
> "With the OCZ Vertex SATA 2.0 SSD, which we used for this testing tod=
ay, had its
> write caching always enabled. When attempting to disable the write ca=
che through
> hdparm it would remain enabled regardless and when using sdparm it wo=
uld report
> change_mode_page: failed setting page: Caching (SBC)."
>
> This invalidates the benchmark! Disabling the write cache would yield=
 a 2X
> improvement.
>
> Digging deeper, I found this:
> http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg07949.html
>
> " Michael,
> =C2=A0My information may be out of date, but last time I
> =C2=A0looked libata didn't support MODE SELECT which is
> =C2=A0the SCSI command to change mode page settings.
> =C2=A0[I have sent patches several times to add support
> =C2=A0for this in libata but ...]
>
> Ahhha!!!
>
> That looks exactly the case.
>
> I tested the two drives (AS and NS ones) on different
> machines, and currently, NS (where things doesn't work)
> is connected to AHCI controller, while the AS one is
> behind mptsas. =C2=A0So it just looks like mptsas is doing
> the right thing in the first place, while ahci (or
> libata, whatever) is failing."
>
> So the article managed to unjustly smear both OCZ Vertex and BTRFS in=
 one shot.

allways take phoronix tests with a very big grain of salt. :-p

usually they are made/prepared "with their eyes closed".. completely
in the dark and they don't diagnose or try to understand the results.
nevertheless, they do test stuff out...


>
> --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 =C2=A0http://vger.kernel.org/majordomo-info.ht=
ml
>



--=20
Miguel Sousa Filipe
--
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

  reply	other threads:[~2009-06-23 10:13 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 [this message]
     [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
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=f058a9c30906230313v10d94a5eg8cf123cef30fb5b8@mail.gmail.com \
    --to=miguel.filipe@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