From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvmove painfully slow on parity RAID
Date: Wed, 29 Dec 2010 21:42:35 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1012292136500.19697@bmsred.bmsi.com> (raw)
In-Reply-To: <4D1B3F6A.4070309@shiftmail.org>
On Wed, 29 Dec 2010, Spelic wrote:
> I tried multiple times for every device with consistent results, so I'm pretty
> sure these are actual numbers.
> What's happening?
> Apart from the amazing difference of parity raid vs nonparity raid, with
> parity raid it seems to vary randomly with the number of devices and the
> chunksize..?
This is pretty much my experience with parity raid all around. Which
is why I stick with raid1 and raid10.
That said, the sequential writes of pvmove should be fast for raid5 *if*
the chunks are aligned so that there is no read/modify/write cycle.
1) Perhaps your test targets are not properly aligned?
2) Perhaps the raid5 implementation (hardware? linux md?
experimental lvm raid5?) does a read modify write even when it
doesn't have to.
Your numbers sure look like read/modify/write is happening for some reason.
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
next prev parent reply other threads:[~2010-12-30 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 2:40 [linux-lvm] pvmove painfully slow on parity RAID Spelic
2010-12-29 14:02 ` Spelic
2010-12-30 2:42 ` Stuart D. Gathman [this message]
2010-12-30 3:13 ` Spelic
2010-12-30 19:12 ` Stuart D. Gathman
2010-12-31 3:41 ` Spelic
2010-12-31 15:36 ` Stuart D. Gathman
2010-12-31 17:23 ` Stuart D. Gathman
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=Pine.LNX.4.64.1012292136500.19697@bmsred.bmsi.com \
--to=stuart@bmsi.com \
--cc=linux-lvm@redhat.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).