All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: MRK <mrk@shiftmail.org>
Cc: Mark Knecht <markknecht@gmail.com>,
	Learner Study <learner.study@gmail.com>,
	linux-raid@vger.kernel.org, keld@dkuug.dk
Subject: Re: Linux Raid performance
Date: Sun, 04 Apr 2010 07:56:38 +1200	[thread overview]
Message-ID: <4BB79D76.7090206@sauce.co.nz> (raw)
In-Reply-To: <4BB7856C.30808@shiftmail.org>

MRK wrote:

> I spent some time trying to optimize it but that was the best I could 
> get. Anyway both my benchmark and Richard's one imply a very significant 
> bottleneck somehwere.

This bottleneck is the SAS controller, at least in my case. I did the 
same math regarding streaming performance of one drive times number of 
drive and wondered where the shortfall was, after tests showed I could 
only streaming read at 850MB/s on the same array.

A query to an LSI engineer got the following response, which basically 
boils down to "you get what you pay for" - SAS vs SATA drives.

"Yes, you're at the "practical" limit.

With that setup and SAS disks, you will exceed 1200 MB/s.  Could go
higher than 1,400 MB/s given the right server chipset.

However with SATA disks, and the way they break up data transfers, 815
to 850 MB/s is the best you can do.

Under SATA, there are multiple connections per I/O request.
   * Command Initiator -> HDD
   * DMA Setup  Initiator -> HDD
   * DMA Activate  HDD -> Initiator
   * Data   HDD -> Initiator
   * Status    HDD -> Initiator
And there is little ability with typical SATA disks to combine traffic
from different I/Os on the same connection.  So you get lots of
individual connections being made, used, & broken.

Contrast that with SAS which has typically 2 connections per I/O, and
will combine traffic from more than 1 I/O per connection.  It uses the
SAS links much more efficiently."


Regards,

Richard

  reply	other threads:[~2010-04-03 19:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 19:42 Linux Raid performance Learner Study
2010-03-31 20:15 ` Keld Simonsen
2010-04-02  3:07   ` Learner Study
2010-04-02  9:58     ` Nicolae Mihalache
2010-04-02 17:58       ` Learner Study
2010-04-02 11:05     ` Keld Simonsen
2010-04-02 11:18       ` Keld Simonsen
2010-04-02 17:55       ` Learner Study
2010-04-02 21:14         ` Keld Simonsen
2010-04-02 21:37           ` Learner Study
2010-04-03 11:20             ` Keld Simonsen
2010-04-03 15:56               ` Learner Study
2010-04-04  1:58                 ` Keld Simonsen
2010-04-03  0:10           ` Learner Study
2010-04-03  0:39         ` Mark Knecht
2010-04-03  1:00           ` John Robinson
2010-04-03  1:14           ` Richard Scobie
2010-04-03  1:32             ` Mark Knecht
2010-04-03  1:37               ` Richard Scobie
2010-04-03  3:06                 ` Learner Study
2010-04-03  3:00             ` Learner Study
2010-04-03 19:27               ` Richard Scobie
2010-04-03 18:14             ` MRK
2010-04-03 19:56               ` Richard Scobie [this message]
2010-04-04 15:00                 ` MRK
2010-04-04 18:26                   ` Learner Study
2010-04-04 18:46                     ` Mark Knecht
2010-04-04 21:28                       ` Jools Wills
2010-04-04 22:38                         ` Mark Knecht
2010-04-05 10:07                           ` Learner Study
2010-04-05 16:35                             ` John Robinson
2010-04-04 22:24                       ` Guy Watkins
2010-04-05 13:49                         ` Drew
2010-04-04 23:24                   ` Richard Scobie
2010-04-05 11:20                     ` MRK
2010-04-05 19:49                       ` Richard Scobie
2010-04-05 21:03                         ` Drew
2010-04-05 22:20                           ` Richard Scobie
2010-04-05 23:49                           ` Roger Heflin
2010-04-14 20:50             ` Bill Davidsen

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=4BB79D76.7090206@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --cc=keld@dkuug.dk \
    --cc=learner.study@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=markknecht@gmail.com \
    --cc=mrk@shiftmail.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.