From: "Jeffrey W. Baker" <jwbaker@acm.org>
To: linux-raid@vger.kernel.org
Subject: Just plain bad RAID5 performance?
Date: Thu, 13 May 2004 17:08:14 -0700 [thread overview]
Message-ID: <1084493294.20832.24.camel@noodles> (raw)
I have this array:
md0 : active raid5 sdb[0] sdd[2] sdc[1]
145225728 blocks level 5, 256k chunk, algorithm 2 [3/3] [UUU]
... on three Western Digital Raptor 74GB drives. These are attached
with a 3ware 8506-8 SATA thingy, the fs is ext2 w/ 4096 block size.
Basic test: dd from all three devices at once. Aggregate I/O: roughly
150MB/sec, > 95% CPU usage. dd from /dev/md0: about 60MB/sec, < 30% CPU
usage. Any way to improve this result? I would expect it to be at
least 100MB/sec.
More complicated test: single postgresql query on a 40GB database.
Query uses three index scans, so it is highly random access. On the
RAID i'm getting about 10-20 tps per device, about 4MB/sec effective
aggregate throughput, according to iostat. On a single 5-year-old SCSI
device I get 1000s of tps and the query finishes roughly 20 times
faster. What could I be seeing here?
The machine is a dual opteron, so I doubt that the CPU is starving the
RAID5 XOR routines or anything silly like that.
Software is: Linux 2.4.26, PostgreSQL 7.4.2.
Any information appreciated.
-jwb
reply other threads:[~2004-05-14 0:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1084493294.20832.24.camel@noodles \
--to=jwbaker@acm.org \
--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