From: Learner Study <learner.study@gmail.com>
To: Richard Scobie <richard@sauce.co.nz>
Cc: Mark Knecht <markknecht@gmail.com>,
linux-raid@vger.kernel.org, keld@dkuug.dk,
learner.study@gmail.com
Subject: Re: Linux Raid performance
Date: Fri, 2 Apr 2010 20:06:14 -0700 [thread overview]
Message-ID: <p2n7efa8a7d1004022006v764c33b6p5a7760885c95b6db@mail.gmail.com> (raw)
In-Reply-To: <4BB69BE1.5090107@sauce.co.nz>
Thanks to everyone for sharing their experiences...this was helpful.
I don't have luxury to have 16 SAS/SATA drives...I guess it would be
great if someone can share results with even higher number of
disks...I would like to know what is the max performance that can be
reached...I understand the theoretical is more like a couple of
Terabytes...but won't we get into some sort of linux file system
related or other kernel bottlenecks as we increase the # of disks?
On Fri, Apr 2, 2010 at 6:37 PM, Richard Scobie <richard@sauce.co.nz> wrote:
> Mark Knecht wrote:
>
>> Richard,
>> Good point. I was limited in my thinking to the sorts of arrays I
>> might use at home being no wider than 3, 4 or 5 disks. However for our
>> N-wide array as N approaches infinity so do the cycles required to run
>> it. I don think that applies to the OP but I don't know that.
>>
>
> I said I thought the busiest CPU was the parity generation one, but in
> hindsight this cannot be correct, as it was almost maxed out at half the
> write speed the array achieved when it was empty.
>
> Regards,
>
> Richard
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-03 3:06 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 [this message]
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
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=p2n7efa8a7d1004022006v764c33b6p5a7760885c95b6db@mail.gmail.com \
--to=learner.study@gmail.com \
--cc=keld@dkuug.dk \
--cc=linux-raid@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=richard@sauce.co.nz \
/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).