linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@keldix.com>
To: David Brown <david@westcontrol.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm raid1 read performance
Date: Thu, 5 May 2011 12:41:57 +0200	[thread overview]
Message-ID: <20110505104156.GA11441@www2.open-std.org> (raw)
In-Reply-To: <iptjde$92f$1@dough.gmane.org>

On Thu, May 05, 2011 at 09:26:45AM +0200, David Brown wrote:
> On 05/05/2011 02:40, Liam Kurmos wrote:
> >Cheers Roberto,
> >
> >I've got the gist of the far layout from looking at wikipedia. There
> >is some clever stuff going on that i had never considered.
> >i'm going for f2 for my system drive.
> >
> >Liam
> >
> 
> For general use, raid10,f2 is often the best choice.  The only 
> disadvantage is if you have applications that make a lot of synchronised 
> writes, as writes take longer (everything must be written twice, and 
> because the data is spread out there is more head movement).  For most 
> writes this doesn't matter - the OS caches the writes, and the app 
> continues on its way, so the writes are done when the disks are not 
> otherwise used.  But if you have synchronous writes, so that the app 
> will wait for the write to complete, it will be slower (compared to 
> raid10,n2 or raid10,o2).

Yes syncroneous writes would be significantly slower.
I have not seen benchmarks on it, tho.
Which applications typically use syncroneous IO?
Maybe not that many.
Do databases do that, eg postgresql and mysql?

> The other problem with raid10 layout is booting - bootloaders don't much 
> like it.  The very latest version of grub, IIRC, can boot from raid10 - 
> but it can be awkward.  There are lots of how-tos around the web for 
> booting when you have raid, but by far the easiest is to divide your 
> disks into partitions:
> 
> sdX1 = 1GB
> sdX2 = xGB
> sdX3 = yGB
> 
> Put all your sdX1 partitions together as raid1 with metadata layout 
> 0.90, format as ext3 and use it as /boot.  Any bootloader will work fine 
> with that (don't forget to install grub on each disk's MBR).
> 
> Put your sdX2 partitions together as raid10,f2 for swap.
> 
> Put the sdX3 partitions together as raid10,f2 for everything else.  The 
> most flexible choice is to use LVM here and make logical partitions for 
> /, /home, /usr, etc.  But you can also partition up the md device in 
> distinct fixed partitions for /, /home, etc. if you want.

there is a similar layout of your disks described in

https://raid.wiki.kernel.org/index.php/Preventing_against_a_failing_disk

> Don't try and make sdX3 and sdX4 groups and raids for separate / and 
> /home (unless you want to use different raid levels for these two 
> groups).  Your disks are faster near the start (at the outer edge of the 
> disk), so you get the best speed by making the raid10,f2 from almost the 
> whole disk.

Hmm, I think the root partition actually would have more accesses than
/home and other partitions, so it may be beneficial to give the fastest
disk sectors to a separate root partition. Comments?

best regards
Keld

  reply	other threads:[~2011-05-05 10:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04  0:07 mdadm raid1 read performance Liam Kurmos
2011-05-04  0:57 ` John Robinson
2011-05-06 20:44   ` Leslie Rhorer
2011-05-06 21:56     ` Keld Jørn Simonsen
2011-05-04  0:58 ` NeilBrown
2011-05-04  5:30   ` Drew
2011-05-04  6:31     ` Brad Campbell
2011-05-04  7:42       ` Roberto Spadim
2011-05-04 23:08         ` Liam Kurmos
2011-05-04 23:35           ` Roberto Spadim
2011-05-04 23:36           ` Brad Campbell
2011-05-04 23:45           ` NeilBrown
2011-05-04 23:57             ` Roberto Spadim
2011-05-05  0:14             ` Liam Kurmos
2011-05-05  0:20               ` Liam Kurmos
2011-05-05  0:25                 ` Roberto Spadim
2011-05-05  0:40                   ` Liam Kurmos
2011-05-05  7:26                     ` David Brown
2011-05-05 10:41                       ` Keld Jørn Simonsen [this message]
2011-05-05 11:38                         ` David Brown
2011-05-06  4:14                           ` CoolCold
2011-05-06  7:29                             ` David Brown
2011-05-06 21:05                       ` Leslie Rhorer
2011-05-07 10:37                         ` David Brown
2011-05-07 10:58                           ` Keld Jørn Simonsen
2011-05-05  0:24               ` Roberto Spadim
2011-05-05 11:10             ` Keld Jørn Simonsen
2011-05-06 21:20               ` Leslie Rhorer
2011-05-06 21:53                 ` Keld Jørn Simonsen
2011-05-07  3:17                   ` Leslie Rhorer
2011-05-05  4:06           ` Roman Mamedov
2011-05-05  8:06             ` Nikolay Kichukov
2011-05-05  8:39               ` Liam Kurmos
2011-05-05  8:49                 ` Liam Kurmos
2011-05-05  9:30               ` NeilBrown
2011-05-04  7:48       ` David Brown

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=20110505104156.GA11441@www2.open-std.org \
    --to=keld@keldix.com \
    --cc=david@westcontrol.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).