From: Johannes Segitz <johannes.segitz@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Performance of a software raid 5
Date: Sun, 26 Apr 2009 19:03:41 +0200 [thread overview]
Message-ID: <a5cd9eed0904261003w28a25a32n4d5017ee41d9e471@mail.gmail.com> (raw)
In-Reply-To: <18925.23969.113047.133385@notabene.brown>
On Tue, Apr 21, 2009 at 7:46 AM, Neil Brown <neilb@suse.de> wrote:
> I suspect you will see that improve when you add another drive that it
> isn't running degraded.
Well, i didn't but it doesn't really matter since the crypto layer slows
it down to a crawl
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
[raid4] [raid10]
md6 : active raid5 sdd1[0] sdc1[1] md7[3] md8[4] sde1[2]
3907039232 blocks level 5, 256k chunk, algorithm 2 [5/5] [UUUUU]
bitmap: 1/15 pages [4KB], 32768KB chunk
md7 : active raid0 sdg1[0] sda1[1]
976767744 blocks 128k chunks
md8 : active raid0 sdh1[1] sdb1[0]
976767744 blocks 128k chunks
So everything is okay now, no missing drive and the bad drive is now gone.
for d in /dev/sd[cde]1 /dev/md[678] /dev/mapper/daten bigfile
do
echo $d
dd if=$d of=/dev/null bs=1M count=1000
done
/dev/sdc1
1048576000 bytes (1.0 GB) copied, 6.13302 s, 171 MB/s
/dev/sdd1
1048576000 bytes (1.0 GB) copied, 12.2261 s, 85.8 MB/s
/dev/sde1
1048576000 bytes (1.0 GB) copied, 11.8026 s, 88.8 MB/s
/dev/md6
1048576000 bytes (1.0 GB) copied, 6.42977 s, 163 MB/s
/dev/md7
1048576000 bytes (1.0 GB) copied, 9.51655 s, 110 MB/s
/dev/md8
1048576000 bytes (1.0 GB) copied, 7.97321 s, 132 MB/s
/dev/mapper/daten
1048576000 bytes (1.0 GB) copied, 28.6309 s, 36.6 MB/s
bigfile
1048576000 bytes (1.0 GB) copied, 31.9715 s, 32.8 MB/s
So the raid works okay, although i'm not thrilled by 163 MB/s
read speed when i see what the underlying devices are capable
of. But the real bad drop seems to be the crypto and with
http://tynne.de/linux-crypto-speed in mind it seems quite a
reasonable speed, although i'm disappointed since i expected
more. Next time i won't expect but do better tests beforehand.
Thanks everyone for their help.
Johannes
next prev parent reply other threads:[~2009-04-26 17:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 17:12 Performance of a software raid 5 Johannes Segitz
2009-04-20 23:46 ` John Robinson
2009-04-21 0:10 ` Johannes Segitz
2009-04-21 0:52 ` John Robinson
2009-04-21 1:05 ` Johannes Segitz
2009-04-21 1:12 ` John Robinson
2009-04-21 1:19 ` NeilBrown
2009-04-21 2:04 ` Johannes Segitz
2009-04-21 5:46 ` Neil Brown
2009-04-21 12:40 ` Johannes Segitz
2009-04-24 13:49 ` Johannes Segitz
2009-04-26 17:03 ` Johannes Segitz [this message]
2009-04-21 18:56 ` Corey Hickey
2009-04-22 12:29 ` Bill Davidsen
2009-04-22 22:32 ` Corey Hickey
2009-04-22 9:07 ` Goswin von Brederlow
2009-04-21 0:44 ` Poor write performance with write-intent bitmap? John Robinson
2009-04-21 1:33 ` NeilBrown
2009-04-21 2:13 ` John Robinson
2009-04-21 5:50 ` Neil Brown
2009-04-21 12:05 ` John Robinson
2009-05-22 23:00 ` Redeeman
2009-04-22 9:16 ` Goswin von Brederlow
2009-04-22 12:41 ` John Robinson
2009-04-22 14:02 ` Goswin von Brederlow
2009-04-23 7:48 ` John Robinson
2009-04-22 14:21 ` Andre Noll
2009-04-23 8:04 ` John Robinson
2009-04-23 20:23 ` Goswin von Brederlow
2009-04-21 16:00 ` 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=a5cd9eed0904261003w28a25a32n4d5017ee41d9e471@mail.gmail.com \
--to=johannes.segitz@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).