linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Learner Study <learner.study@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Linux Raid performance
Date: Mon, 05 Apr 2010 17:35:35 +0100	[thread overview]
Message-ID: <4BBA1157.10409@anonymous.org.uk> (raw)
In-Reply-To: <o2h7efa8a7d1004050307wec888a73tc297827a0ea6cf8d@mail.gmail.com>

On 05/04/2010 11:07, Learner Study wrote:
> Hi Mark, all:
> 
> My apologies if I sounded like a pest by asking too many
> questions...

Don't worry about it, but do take care - I'm afraid I was similarly 
sceptical about the email alias you've chosen, and got the impression 
from some of your questions that you might be a kid asking people here 
to do your homework for you, which does happen from time to time.

> Since I don't have access to array of disks, I sought to
> the list to see if I could use the info already out there instead of
> reinventing it...how well suited is linux raid for 10G kind of
> traffic..

If you mean 10G bits per second, or at least enough for a 10GigE 
network, then yes I think it is, as evidenced by people here saying 
they've got up to 1400MB/s, as long as you've got enough really fast SAS 
drives hooked up via high-class SAS interfaces over wide PCI Express 
buses to Xeon CPUs with fast RAM, though none of this is exactly 
commodity-class hardware.

As far as I know, 10G bytes per second is beyond PC hardware at the 
moment, and I have no knowledge or experience of the kinds of hardware 
that could reach those speeds.

You got me thinking about the bottlenecks, though. Just for fun (so you 
can see what an odd idea of fun I have), I just restarted my big storage 
server box (Core 2 Quad 3.2GHz on 1600MHz FSB, dual-channel DDR2-800 
memory, Intel P45/ICH10R motherboard) into memtest86+, and it's telling 
me that my memory bandwidth is 4.5GB/s. That's probably about the limit 
of this architecture, though the newer Core i5/7 chips with dual- and 
triple-channel memory controllers integrated can probably manage more.

Now, if I'm running RAID-5 or 6, and Linux md has to copy every page I 
want to write to disc (therefore read it from RAM and write it back 
again), and then read it again to calculate the parity block(s), then 
the SATA/SAS controllers have to read it, that's at least 4 memory 
operations for every write to disc, which is going to mean there's a 
memory subsystem bottleneck/throttle on this machine of about 
1.125GB/sec. I skipped over the bit where I have to write the parity to 
RAM and also have the SATA/SAS controllers read that to write it to the 
disc, but that's going to make a fairly modest difference, maybe down to 
1GB/sec. Since my CPU can calculate RAID-5 or 6 parity on a single core 
at 8GB/sec, that's not the bottleneck.

And I do understand that I'd be rather optimistic to think my RAM 
bandwidth was as much as 4.5GB/s for much of the time.

Reads should be quicker though :-)

Cheers,

John.

  reply	other threads:[~2010-04-05 16:35 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
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 [this message]
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=4BBA1157.10409@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=learner.study@gmail.com \
    --cc=linux-raid@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).