From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Andrew Clayton <andrew@pccl.info>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 5 performance issue.
Date: Wed, 03 Oct 2007 19:53:08 +0200 [thread overview]
Message-ID: <87r6kcccfv.fsf@informatik.uni-tuebingen.de> (raw)
In-Reply-To: <20071003105321.06943824@zeus.pccl.info> (Andrew Clayton's message of "Wed, 3 Oct 2007 10:53:21 +0100")
Andrew Clayton <andrew@pccl.info> writes:
> Hi,
>
> Hardware:
>
> Dual Opteron 2GHz cpus. 2GB RAM. 4 x 250GB SATA hard drives. 1 (root file system) is connected to the onboard Silicon Image 3114 controller. The other 3 (/home) are in a software RAID 5 connected to a PCI Silicon Image 3124 card. I moved the 3 raid disks off the on board controller onto the card the other day to see if that would help, it didn't.
I would think the onboard controller is connected to the north or
south bridge and possibly hooked directly into the hyper
transport. The extra controler is PCI so you are limited to
theoretical 128MiB/s. For me the onboard chips do much better (though
at higher cpu cost) than pci cards.
MfG
Goswin
next prev parent reply other threads:[~2007-10-03 17:53 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 9:53 RAID 5 performance issue Andrew Clayton
2007-10-03 16:43 ` Justin Piszcz
2007-10-03 16:48 ` Justin Piszcz
2007-10-03 20:10 ` Andrew Clayton
2007-10-03 20:16 ` Justin Piszcz
2007-10-06 12:30 ` Justin Piszcz
2007-10-06 16:05 ` Justin Piszcz
2007-10-03 20:19 ` Andrew Clayton
2007-10-03 20:35 ` Justin Piszcz
2007-10-03 20:46 ` Andrew Clayton
2007-10-03 20:36 ` David Rees
2007-10-03 20:48 ` Andrew Clayton
2007-10-04 14:08 ` Andrew Clayton
2007-10-04 14:09 ` Justin Piszcz
2007-10-04 14:10 ` Justin Piszcz
2007-10-04 14:44 ` Andrew Clayton
2007-10-04 16:20 ` Justin Piszcz
2007-10-04 18:26 ` Andrew Clayton
2007-10-05 10:25 ` Justin Piszcz
2007-10-05 10:57 ` Andrew Clayton
2007-10-05 11:08 ` Justin Piszcz
2007-10-05 12:53 ` Andrew Clayton
2007-10-05 13:18 ` Justin Piszcz
2007-10-05 13:30 ` Andrew Clayton
2007-10-05 14:07 ` Justin Piszcz
2007-10-05 14:32 ` Andrew Clayton
2007-10-05 16:10 ` Andrew Clayton
2007-10-05 16:16 ` Justin Piszcz
2007-10-05 19:33 ` Andrew Clayton
2007-10-05 18:58 ` Richard Scobie
2007-10-05 19:02 ` Justin Piszcz
2007-10-05 19:02 ` John Stoffel
2007-10-05 19:42 ` Andrew Clayton
2007-10-05 20:56 ` John Stoffel
2007-10-07 17:22 ` Andrew Clayton
2007-10-11 17:06 ` Bill Davidsen
2007-10-11 18:07 ` Andrew Clayton
2007-10-11 23:43 ` Justin Piszcz
2007-10-04 14:36 ` Andrew Clayton
2007-10-04 14:39 ` Justin Piszcz
2007-10-04 15:03 ` Andrew Clayton
2007-10-04 16:19 ` Justin Piszcz
2007-10-04 19:01 ` Andrew Clayton
2007-10-04 16:46 ` Steve Cousins
2007-10-04 17:06 ` Steve Cousins
2007-10-04 19:06 ` Andrew Clayton
2007-10-05 10:20 ` Justin Piszcz
2007-10-04 14:39 ` Justin Piszcz
2007-10-03 17:53 ` Goswin von Brederlow [this message]
2007-10-03 20:20 ` Andrew Clayton
2007-10-03 20:48 ` Richard Scobie
2007-10-05 20:25 ` Brendan Conoboy
2007-10-06 0:38 ` Dean S. Messing
2007-10-06 8:18 ` Justin Piszcz
2007-10-08 1:40 ` Dean S. Messing
2007-10-08 8:44 ` Justin Piszcz
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=87r6kcccfv.fsf@informatik.uni-tuebingen.de \
--to=brederlo@informatik.uni-tuebingen.de \
--cc=andrew@pccl.info \
--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).