From: Richard Scobie <r.scobie@clear.net.nz>
To: linux-ide@vger.kernel.org
Subject: SAS v SATA interface performance
Date: Sat, 01 Dec 2007 08:19:19 +1300 [thread overview]
Message-ID: <47506237.3000406@clear.net.nz> (raw)
If one disregards the rotational speed and access time advantage that
SAS drives have over SATA, does the SAS interface offer any performance
advantage?
For example, assume a SAS drive and a SATA drive can both sustained
stream 70MB/s. A 16 drive JBOD SAS enclosure with internal SAS expander
is connected via a 4port SAS RAID controller, configured for RAID 5
across all 16 drives.
If tests are then run reading and writing a multi gigabyte file to empty
arrays made up of 16 SAS drives and 16 SATA drives, would the results be
identical?
I ask, as I have seen a comment to the effect that SATA drives are less
efficient interacting at the bus/interface level in this situation, but
I have had no luck confirming this after extensive searching.
Regards,
Richard
next reply other threads:[~2007-11-30 19:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 19:19 Richard Scobie [this message]
2007-11-30 21:24 ` SAS v SATA interface performance Michael Tokarev
2007-11-30 23:17 ` Alan Cox
2007-12-01 7:43 ` Richard Scobie
2007-12-01 14:37 ` Greg Freemyer
2007-12-01 19:19 ` Richard Scobie
2007-12-01 20:01 ` Mark Lord
2007-12-01 20:40 ` Jeff Garzik
2007-12-01 23:55 ` Richard Scobie
2007-12-02 3:45 ` Mark Lord
2007-12-02 3:49 ` Mark Lord
2007-12-10 7:33 ` Tejun Heo
2007-12-10 14:36 ` Jens Axboe
2007-12-10 16:28 ` Mark Lord
2007-12-10 14:50 ` James Bottomley
2007-12-10 16:32 ` Mark Lord
-- strict thread matches above, loose matches on Subject: below --
2007-12-01 0:04 Richard Scobie
2007-12-01 0:17 ` Alan Cox
2007-12-01 3:06 ` Mark Lord
2007-12-10 7:15 ` Tejun Heo
2007-12-10 16:23 ` Mark Lord
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=47506237.3000406@clear.net.nz \
--to=r.scobie@clear.net.nz \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.