linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Mirko Benz <mirko.benz@web.de>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID 5 write performance advice
Date: Wed, 24 Aug 2005 08:46:28 -0400	[thread overview]
Message-ID: <1124887589.5550.27.camel@localhost.localdomain> (raw)
In-Reply-To: <430C2EA6.2050103@web.de>

On Wed, 2005-08-24 at 10:24 +0200, Mirko Benz wrote:
> Hello,
> 
> We have recently tested Linux 2.6.12 SW RAID versus HW Raid. For SW Raid 
> we used Linux 2.6.12 with 8 Seagate SATA NCQ disks no spare on a Dual 
> Xeon platform. For HW Raid we used a Arc-1120 SATA Raid controller and a 
> Fibre Channel Raid System (Dual 2 Gb, Infortrend).
> 
> READ     SW:877 ARC:693 IFT:366
> (MB/s @64k BS using disktest with raw device)
> 
> Read SW Raid performance is better than HW Raid. The FC RAID is limited 
> by the interface.
> 
> WRITE    SW:140 ARC:371 IFT:352
> 
> For SW RAID 5 we needed to adjust the scheduling policy. By default we 
> got only 60 MB/s. SW RAID 0 write performance @64k is 522 MB/s.
how u test and get these number?

what is u raid5 configuration? chunk size?

> 
> Based on the performance numbers it looks like Linux SW RAID reads every 
> data element of a stripe + parity in parallel, performs xor operations 
> and than writes the data back to disk in parallel.
> 
> The HW Raid controllers seem to be a bit smarter in this regard. When 
> they encounter a large write with enough data for a full stripe they 
> seem to spare the read and perform only the xor + write in parallel. 
> Hence no seek is required and in can be closer to RAID0 write performance.
this is stripe write and linux MD have this.



> 
> We have an application were large amounts of data need to be 
> sequentially written to disk (e.g. 100 MB at once). The storage system 
> has an USV so write caching can be utilized.
> 
> I would like to have an advice if write performance similar to HW Raid 
> controllers is possible with Linux or if there is something else that we 
> could apply.
> 
> Thanks in advance,
> Mirko
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2005-08-24 12:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24  8:24 RAID 5 write performance advice Mirko Benz
2005-08-24 12:46 ` Ming Zhang [this message]
2005-08-24 13:43   ` Mirko Benz
2005-08-24 13:49     ` Ming Zhang
2005-08-24 21:32     ` Neil Brown
2005-08-25 16:38       ` Mirko Benz
2005-08-25 16:54         ` Ming Zhang
2005-08-26  7:51           ` Mirko Benz
2005-08-26 14:26             ` Ming Zhang
2005-08-26 14:30             ` Ming Zhang
2005-08-26 15:29               ` Mirko Benz
2005-08-26 17:05                 ` Ming Zhang
2005-08-28 23:28                 ` Neil Brown
2005-09-01 19:44         ` djani22

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=1124887589.5550.27.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=mirko.benz@web.de \
    /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).