All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Michael Evans <mjevans1983@gmail.com>,
	Kaushal Shriyan <kaushalshriyan@gmail.com>,
	linux-raid@vger.kernel.org
Subject: Re: RAID5
Date: Sun, 02 May 2010 18:51:54 -0400	[thread overview]
Message-ID: <4BDE020A.9060602@tmr.com> (raw)
In-Reply-To: <4BD1AE0C.2040003@msgid.tls.msk.ru>

Michael Tokarev wrote:
> Michael Evans wrote:
>   
>> On Wed, Apr 21, 2010 at 6:32 AM, Bill Davidsen <davidsen@tmr.com> wrote:
>>     
> []
>   
>>> I have some recent experience with this gained the hard way, by looking for
>>> a problem rather than curiousity. My experience with LVM on RAID is that, at
>>> least for RAID-5, write performance sucks. I created two partitions on each
>>> of three drives, and two raid-5 arrays using those partitions. Same block
>>> size, same tuning for stripe-cache, etc. I dropped an ext4 on on array, and
>>> LVM on the other, put ext4 on the LVM drive, and copied 500GB to each. LVM
>>> had a 50% performance penalty, took twice as long. Repeated with four drives
>>> (all I could spare) and found that the speed right on an array was roughly
>>> 3x slower with LVM.
>>>
>>>       
>> This issues sounds very likely to be write barrier related.  Were you
>> using an external journal on a write-barrier honoring device?
>>     
>
> This is most likely due to read-modify-write cycle which is present on
> lvm-on-raid[456] if the number of data drives is not a power of two.
> LVM requires the block size to be a power of two, so if you can't fit
> some number of LVM blocks on whole raid stripe size your write speed
> is expected to be ~3 times worse...
>
>   
Since I tried 3 and 4 drive setups, with several chunk sizes, I would 
hope that no matter how lvm counts data drives (why does it care?) it 
would find a power of two there.
> Even creating partitions on such raid array is difficult.
>
> 'Hwell.
>
> Unfortunately very few people understand this.
>
> As of write barriers, it looks like either they already work
> (in 2.6.33) or will be (in 2.6.34) for whole raid5-lvm stack.
>
> /mjt
> --
> 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
>
>   


-- 
Bill Davidsen <davidsen@tmr.com>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein


  parent reply	other threads:[~2010-05-02 22:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  3:46 RAID5 Kaushal Shriyan
2010-04-19  4:21 ` RAID5 Michael Evans
2010-04-21 13:32   ` RAID5 Bill Davidsen
2010-04-21 19:43     ` RAID5 Michael Evans
2010-04-23 14:26       ` RAID5 Michael Tokarev
2010-04-23 14:57         ` RAID5 MRK
2010-04-23 20:57         ` RAID5 Michael Evans
2010-04-24  1:47           ` RAID5 Mikael Abrahamsson
2010-04-24  3:34             ` RAID5 Michael Evans
2010-05-02 22:51         ` Bill Davidsen [this message]
2010-05-03  5:51         ` RAID5 Luca Berra
2010-05-02 22:45       ` RAID5 Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2016-03-01 14:24 raid5 John Smith
2016-03-01 21:44 ` raid5 Duncan
2016-03-02 13:43   ` raid5 Austin S. Hemmelgarn
2016-03-03  4:16     ` raid5 Duncan

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=4BDE020A.9060602@tmr.com \
    --to=davidsen@tmr.com \
    --cc=kaushalshriyan@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjevans1983@gmail.com \
    --cc=mjt@tls.msk.ru \
    /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.