From: Mirko Benz <mirko.benz@web.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: dougg@torque.net, linux-scsi@vger.kernel.org
Subject: Re: SATA on mptsas performance
Date: Wed, 01 Mar 2006 09:16:14 +0100 [thread overview]
Message-ID: <4405584E.6070806@web.de> (raw)
In-Reply-To: <44053A8E.6000206@pobox.com>
Hello,
As promised we have tested 3 Gb (aka SATA II) disks.
Configuration: LSI SAS3442X controller, Promise SAS JBOD, 12 disks
Seagate SATA 80 GB
Tested with parallel dd invocations with bs=32k.
The results look better:
# disks Read AVG Write AVG
1 69 69,0 68 68,0
6 420 70,0 324 54,0
7 459 65,6 367 52,4
8 426 53,3 394 49,3
9 399 44,3 389 43,2
10 410 41,0 431 43,1
11 438 39,8 428 38,9
12 468 39,0 481 40,1
Available bandwidth is 4 * 3 Gb = 1.5 GB (4 lanes / external wide SAS
port).
So there is still some room for improvement. Has anyone else a similar
setup and can provide results?
Maybe with the Adaptec SAS controller?
Thanks,
Mirko
Jeff Garzik schrieb:
> Douglas Gilbert wrote:
>> If the SATA disk does 3 Gb/sec then yes but SATA-1 disks
>> run at 1.5 Gb/sec (and don't have NCQ). When a SAS HBA
>
> To further confuse things, "SATA-1", "SATA-2", etc. don't mean much at
> all. I recommend never using these terms.
>
> There are many disks that can do NCQ but not 3 Gb/sec, for example.
>
> Its best just to mention the existence of features, because there is
> no __technical__ definition of "SATA 2" that one can test in software.
> SATA 2 is just a set of features defined by marketing.
>
> Jeff
>
>
next prev parent reply other threads:[~2006-03-01 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 16:02 SATA on mptsas performance Moore, Eric
2006-02-15 7:52 ` Mirko Benz
2006-03-01 3:30 ` Douglas Gilbert
2006-03-01 6:09 ` Jeff Garzik
2006-03-01 8:16 ` Mirko Benz [this message]
2006-03-01 17:55 ` Asgeir Eiriksson
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 16:04 Moore, Eric
2006-02-13 14:01 Mirko Benz
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=4405584E.6070806@web.de \
--to=mirko.benz@web.de \
--cc=dougg@torque.net \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).