linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@keldix.com>
To: Erwan MAS <erwan@mas.nom.fr>
Cc: Matt Tehonica <matt.tehonica@mac.com>, linux-raid@vger.kernel.org
Subject: Re: Typical RAID5 transfer speeds
Date: Sun, 20 Dec 2009 11:31:11 +0100	[thread overview]
Message-ID: <20091220103110.GA11852@rap.rap.dk> (raw)
In-Reply-To: <20091220100450.GE15757@voyageur.mas.nom.fr>

On Sun, Dec 20, 2009 at 11:04:50AM +0100, Erwan MAS wrote:
> On Fri, Dec 18, 2009 at 07:37:20PM -0500, Matt Tehonica wrote:
> > I have a 4 disk RAID5 using a 2048K chunk size and using XFS  
> > filesystem.  Typical file size is about 2GB-5GB. I usually get around  
> > 50MB/sec transfer speed when writting files to the array. Is this  
> > typcial or is it below normal?  A friend has a 20 disk RAID6 using the  
> > same filesystem and chunk size and gets around 150MB/sec. Any input on  
> > this??
> 
> You must be aware :
>  - each disk has physical limitations that depends from rpm
>  - that writing is slow on raid5 & raid6 .
> 
> With a raid5 device ,when writing a new block , you must :
>   - read the original block
>   - read the parity   block
>   - compute the new parity
>   - write the new block
>   - write the new parity
> 
> With a raid6 device ,when writing a new block , you must :
>   - read the original block
>   - read the parity 1  block
>   - read the parity 2  block
>   - compute the new parity 1
>   - compute the new parity 2
>   - write the new block
>   - write the new parity 1
>   - write the new parity 2
> 
> With cache , you can have better performance somes times , that depends of usage of device
> by the application .

There is also a mode for writing that detects that you are wiping many
blocks, and thus does not read the parity blocks nor the original
blocks. This is good for writing big files. The kernel detects this mode
for you, eg when writing large sequential files.


> Its'common to said that :
>   on raid 5    you have x4 penalty in writing 
>   on raid 6    you have x6 penalty in writing 
>   on raid 1/10 you have x2 penalty in writing 
>   on raid 0    you have no penalty in writing 

In the sequential mode, the penalty is then only 1 parity drive writing
for RAID5, and 2 drive writing for RAID6. This RAID5/6 can be much
faster than RAID1 (and RAID10) for writing.


> Its'common to said that :
>   one  15k rpm drive can do 180 random IO per second
>   one  10k rpm drive can do 140 random IO per second
>   one 7200 rpm drive can do  80 random IO per second

The elevator algorithm used can du much to improve these rates.

> If you have perfomance problem you must have more drive, because more drive give you more iops .

Or, if IOPS is your concern, then try SSD.

> If you have bad perfomance with raid5 during write you must try raid1 .
> 
> It's better to have many small disks that a big one , for perfomance . 
> 
> But for Electricity consumption , it's different :
>  2,5 drive use less electricity that 3,5 drive
>  slower in RPM drive use lesser electricity 
> 
> There no magic formula !
> 
> In your case :
>  you used 4 drives in raid5 , so when you write data , you have only the performance of one drive .
>  number_of_disk_in_the_array / 4 ( because you are in raid5 )
> 
> For your friend :
>  He used a 20 drives in raid6 , so when he write data , he have performance of 3.6 drives
>  number_of_disk_in_the_array / 6 ( because you are in raid6 )

Best regards
keld

  reply	other threads:[~2009-12-20 10:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19  0:37 Typical RAID5 transfer speeds Matt Tehonica
2009-12-19  1:05 ` Bernd Schubert
2009-12-19  8:30   ` Thomas Fjellstrom
2009-12-19  9:38     ` Michael Evans
2009-12-19 11:43   ` John Robinson
2009-12-19 19:18     ` Leslie Rhorer
2009-12-21 13:06       ` Goswin von Brederlow
2009-12-19 21:35 ` Roger Heflin
2009-12-20  4:21   ` Michael Evans
2009-12-20  9:55     ` Thomas Fjellstrom
2009-12-20 14:53       ` Andre Tomt
2009-12-20 16:03         ` Thomas Fjellstrom
2009-12-20 18:28     ` Roger Heflin
2009-12-21  1:18       ` Michael Evans
2009-12-21  1:50         ` Richard Scobie
2009-12-21 11:30           ` Asdo
2009-12-21 18:28             ` Richard Scobie
2009-12-20 10:04 ` Erwan MAS
2009-12-20 10:31   ` Keld Jørn Simonsen [this message]
2009-12-20 15:25 ` Andre Tomt

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=20091220103110.GA11852@rap.rap.dk \
    --to=keld@keldix.com \
    --cc=erwan@mas.nom.fr \
    --cc=linux-raid@vger.kernel.org \
    --cc=matt.tehonica@mac.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 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).