All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Freemyer <greg.freemyer@gmail.com>
To: Jon@ehardcastle.com
Cc: Goswin von Brederlow <goswin-v-b@web.de>, linux-raid@vger.kernel.org
Subject: Re: Adding more drives/saturating the bandwidth
Date: Tue, 31 Mar 2009 09:05:46 -0400	[thread overview]
Message-ID: <87f94c370903310605p893c6ces5ae3ee4e274c3b22@mail.gmail.com> (raw)
In-Reply-To: <439371.59188.qm@web51306.mail.re2.yahoo.com>

On Tue, Mar 31, 2009 at 4:23 AM, Jon Hardcastle <jd_hardcastle@yahoo.com> wrote:
>
> --- On Mon, 30/3/09, Goswin von Brederlow <goswin-v-b@web.de> wrote:
>
>> From: Goswin von Brederlow <goswin-v-b@web.de>
>> Subject: Re: Adding more drives/saturating the bandwidth
>> To: Jon@eHardcastle.com
>> Cc: linux-raid@vger.kernel.org
>> Date: Monday, 30 March, 2009, 4:40 PM
>> Jon Hardcastle <jd_hardcastle@yahoo.com> writes:
>>
>> > Hey guys, How do you know if your machine can handle
>> adding some more drives to it? How can you check that there
>> is enough BUS IO to handle extra sata cards and also that
>> the machine is powerful enough to support say an 8 drive
>> raid 5...
>>
>> A) Try & error.
>> B) look up the speed of the bus and half it. Any bandwidth
>> left?
>>    make sure the cpu isn't at 100% already as well
>>
>> MfG
>>         Goswin
>
> Cheers guys, I dont think CPU will be an issue as when i looked yesterday whilst copying to my 6 drive raid 5 array it was at ~10% (the only time i get access issues is when i am smart checking all 6 discs and trying to stream a movie of it at the same time!)
>
> As for try and error... sounds scary as once I have added a drive to the array I can undo the process!

What do you think the "ran out of bandwidth" error is.  You make it
sound fatal.  Not true, it is just a bottleneck.  So if you design
your system to max out the bus structure with a a random i/o load, but
then you perform a large sequential load, the sequential workload will
just under perform what you would expect based on the disk drives
themselves.

No big deal as long as you design and test based on your real world workload.

Greg
-- 
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
--
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

  reply	other threads:[~2009-03-31 13:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 12:43 Adding more drives/saturating the bandwidth Jon Hardcastle
2009-03-30 15:40 ` Goswin von Brederlow
2009-03-30 16:28   ` Nagilum
2009-03-31  8:23   ` Jon Hardcastle
2009-03-31 13:05     ` Greg Freemyer [this message]
2009-03-31 21:07     ` Goswin von Brederlow
2009-04-01  8:15       ` Jon Hardcastle
2009-04-01  8:56       ` Jon Hardcastle
2009-04-01 15:59         ` Goswin von Brederlow
2009-04-01 16:15           ` Greg Freemyer
2009-04-01 14:56       ` Andrew Burgess
2009-04-01 15:17         ` David Lethe
2009-04-01 18:06         ` Goswin von Brederlow
2009-04-01 18:57           ` Richard Scobie
2009-04-03 20:42             ` Goswin von Brederlow
2009-04-03 21:06               ` Robin Hill

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=87f94c370903310605p893c6ces5ae3ee4e274c3b22@mail.gmail.com \
    --to=greg.freemyer@gmail.com \
    --cc=Jon@ehardcastle.com \
    --cc=goswin-v-b@web.de \
    --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 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.