From: Mike Ramsey <MikeJRamsey@comcast.net>
To: linux-btrfs@vger.kernel.org
Subject: Phoronix article slaming BTRFS
Date: Tue, 23 Jun 2009 02:51:41 +0000 (UTC) [thread overview]
Message-ID: <loom.20090623T024010-331@post.gmane.org> (raw)
I ran across this article "Testing Out The SSD Mode In Btrfs".
http://www.phoronix.com/scan.php?page=article&item=btrfs_ssd_mode&num=1
At first I was disappointed. It gave a very disappointing set of benchmarks.
However, a close reading revealed this:
"With the OCZ Vertex SATA 2.0 SSD, which we used for this testing today, had its
write caching always enabled. When attempting to disable the write cache through
hdparm it would remain enabled regardless and when using sdparm it would 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,
My information may be out of date, but last time I
looked libata didn't support MODE SELECT which is
the SCSI command to change mode page settings.
[I have sent patches several times to add support
for 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. So 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.
--Mike Ramsey
next reply other threads:[~2009-06-23 2:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 2:51 Mike Ramsey [this message]
2009-06-23 10:13 ` Phoronix article slaming BTRFS 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
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.20090623T024010-331@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