All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: maobo <maobo1983@gmail.com>
Cc: Jon Nelson <jnelson@jamponi.net>,
	Janek Kozicki <janek_listy@wp.pl>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid10: unfair disk load?
Date: Sun, 23 Dec 2007 15:36:04 +0300	[thread overview]
Message-ID: <476E5634.4050607@msgid.tls.msk.ru> (raw)
In-Reply-To: <beb6123c0712222034g68743afv31c644ff4dd9aaff@mail.gmail.com>

maobo wrote:
> Hi,all
> Yes, Raid10 read balance is the shortest position time first and
> considering the sequential access condition. But its performance is
> really poor from my test than raid0.

Single-stream write performance of raid0, raid1 and raid10 should be
of similar level (with raid5 and raid6 things are different) -- in all
3 cases, it should be near the write speed of a single drive.  The
only possible problematic cases is when you've some "unlucky" hardware
which does not permit writing into two drives in parallel - in which
case raid1 and raid10 write speed should be less than to raid0 and
single drive.  But even ol'good IDE drives/controllers, even if two
disks are on the same channel, permits parallel writes.  Modern SATA
and SCSI/SAS should be no problem - hopefully, modulo (theoretically)
some very cheap lame controllers.

> I think this is the process flow raid10 influence. But RAID0 is so
> simple and performed very well!
> From this point that striping is better than mirroring! RAID10 is
> stipe+mirror. But for write condition it performed really bad than RAID0.
> Isn't it?

No it's not.  When the hardware (and drivers) is sane anyway.

Also, "speed" is a very objective thing, so to say - it very much
depends on the workload.

/mjt

  parent reply	other threads:[~2007-12-23 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <476BA4FD.6080401@msgid.tls.msk.ru>
2007-12-21 11:53 ` raid10: unfair disk load? Michael Tokarev
2007-12-21 16:49   ` Janek Kozicki
2007-12-21 20:56     ` Michael Tokarev
2007-12-22 12:05       ` Janek Kozicki
2007-12-22 13:04         ` Jon Nelson
     [not found]           ` <beb6123c0712222034g68743afv31c644ff4dd9aaff@mail.gmail.com>
2007-12-23 12:36             ` Michael Tokarev [this message]
     [not found]               ` <beb6123c0712230521r2a8a43aboe097fc2fc943c3ae@mail.gmail.com>
2007-12-23 14:23                 ` Jon Nelson
2007-12-23 19:22                   ` Richard Scobie
2007-12-25 20:18                     ` 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=476E5634.4050607@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=janek_listy@wp.pl \
    --cc=jnelson@jamponi.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=maobo1983@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.