All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Nagel <thiemo.nagel@ph.tum.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Norman Elton <normelton@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Raid over 48 disks
Date: Tue, 18 Dec 2007 22:13:26 +0100	[thread overview]
Message-ID: <476837F6.7050404@ph.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0712181523250.7823@p34.internal.lan>

>> Performance of the raw device is fair:
>> # dd if=/dev/md2 of=/dev/zero bs=128k count=64k
>> 8589934592 bytes (8.6 GB) copied, 15.6071 seconds, 550 MB/s
>>
>> Somewhat less through ext3 (created with -E stride=64):
>> # dd if=largetestfile of=/dev/zero bs=128k count=64k
>> 8589934592 bytes (8.6 GB) copied, 26.4103 seconds, 325 MB/s
> 
> Quite slow?
> 
> 10 disks (raptors) raid 5 on regular sata controllers:
> 
> # dd if=/dev/md3 of=/dev/zero bs=128k count=64k
> 8589934592 bytes (8.6 GB) copied, 10.718 seconds, 801 MB/s
> 
> # dd if=bigfile of=/dev/zero bs=128k count=64k
> 3640379392 bytes (3.6 GB) copied, 6.58454 seconds, 553 MB/s

Interesting.  Any ideas what could be the reason?  How much do you get 
from a single drive?  -- The Samsung HD501LJ that I'm using gives 
~84MB/s when reading from the beginning of the disk.

With RAID 5 I'm getting slightly better results (though I really wonder 
why, since naively I would expect identical read performance) but that 
does only account for a small part of the difference:

	16k read	64k write
chunk
size	RAID 5	RAID 6	RAID 5	RAID 6
128k	492	497	268	270
256k	615	530	288	270
512k	625	607	230	174
1024k	650	620	170	75

Kind regards,

Thiemo

  reply	other threads:[~2007-12-18 21:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 17:29 Raid over 48 disks Norman Elton
2007-12-18 18:27 ` Justin Piszcz
2007-12-18 19:34   ` Thiemo Nagel
2007-12-18 19:52     ` Norman Elton
2007-12-18 20:19       ` Thiemo Nagel
2007-12-18 20:25     ` Justin Piszcz
2007-12-18 21:13       ` Thiemo Nagel [this message]
2007-12-18 21:20         ` Jon Nelson
2007-12-18 21:40           ` Thiemo Nagel
2007-12-18 21:43           ` Justin Piszcz
2007-12-18 21:21         ` Justin Piszcz
2007-12-19 15:21         ` Bill Davidsen
2007-12-19 15:02           ` Justin Piszcz
2007-12-20 16:48           ` Thiemo Nagel
2007-12-21  1:53             ` Bill Davidsen
2007-12-18 18:45 ` Robin Hill
2007-12-18 20:28 ` Neil Brown
2007-12-19  8:27   ` Mattias Wadenstein
2007-12-19 15:26     ` Bill Davidsen
2007-12-21 11:03     ` Leif Nixon
2007-12-25 17:31   ` pg_mh, Peter Grandi
2007-12-25 21:08     ` Bill Davidsen
2007-12-18 20:36 ` Brendan Conoboy
2007-12-18 23:50   ` Guy Watkins
2007-12-18 23:58     ` Justin Piszcz
2007-12-18 23:59       ` Justin Piszcz
2007-12-19 12:08     ` Russell Smith
2007-12-21 10:57 ` Leif Nixon

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=476837F6.7050404@ph.tum.de \
    --to=thiemo.nagel@ph.tum.de \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=normelton@gmail.com \
    /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.