From: Peter Rabbitson <rabbit+list@rabbit.us>
To: Oliver Martin <oliver.martin@student.tuwien.ac.at>
Cc: Janek Kozicki <janek_listy@wp.pl>, linux-raid@vger.kernel.org
Subject: Re: LVM performance
Date: Wed, 20 Feb 2008 00:19:27 +0100 [thread overview]
Message-ID: <47BB63FF.3040202@rabbit.us> (raw)
In-Reply-To: <47BB30DF.1080006@student.tuwien.ac.at>
Oliver Martin wrote:
> Interesting. I'm seeing a 20% performance drop too, with default RAID
> and LVM chunk sizes of 64K and 4M, respectively. Since 64K divides 4M
> evenly, I'd think there shouldn't be such a big performance penalty.
I am no expert, but as far as I have read you must not only have compatible
chunk sizes (which is easy and most often the case). You also must stripe
align the LVM chunks, so every chunk spans an even number of raid stripes (not
raid chunks). Check the output of `dmsetup table`. The last number is the
offset of the underlying block device at which the LVM data portion starts. It
must be divisible by the raid stripe length (the length varies for different
raid types).
Currently LVM does not offer an easy way to do such alignment, you have to do
it manually upon executing pvcreate. By using the option --metadatasize one
can specify the size of the area between the LVM header (64KiB) and the start
of the data area. So one would supply STRIPE_SIZE - 64 for metadatasize[*],
and the result will be a stripe aligned LVM.
This information is unverified, I just compiled it from different list threads
and whatnot. I did this to my own arrays/volumes and I get near 100% raw
speed. If someone else can confirm the validity of this - it would be great.
Peter
* The supplied number is always rounded up to be divisible by 64KiB, so the
smallest total LVM header is at least 128KiB
next prev parent reply other threads:[~2008-02-19 23:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 3:58 RAID5 to RAID6 reshape? Beolach
2008-02-17 11:50 ` Peter Grandi
2008-02-17 14:45 ` Conway S. Smith
2008-02-18 5:26 ` Janek Kozicki
2008-02-18 12:38 ` Beolach
2008-02-18 14:42 ` Janek Kozicki
2008-02-19 19:41 ` LVM performance (was: Re: RAID5 to RAID6 reshape?) Oliver Martin
2008-02-19 19:52 ` Jon Nelson
2008-02-19 20:00 ` Iustin Pop
2008-02-19 23:19 ` Peter Rabbitson [this message]
2008-02-20 12:19 ` Peter Grandi
2008-02-22 13:41 ` LVM performance Oliver Martin
2008-03-07 8:14 ` Peter Grandi
2008-03-09 19:56 ` Oliver Martin
2008-03-09 21:13 ` Michael Guntsche
2008-03-09 23:27 ` Oliver Martin
2008-03-09 23:53 ` Michael Guntsche
2008-03-10 8:54 ` Oliver Martin
2008-03-10 21:04 ` Peter Grandi
2008-03-12 14:03 ` Michael Guntsche
2008-03-12 19:54 ` Peter Grandi
2008-03-12 20:11 ` Guntsche Michael
2008-03-10 0:32 ` Richard Scobie
2008-03-10 0:53 ` Michael Guntsche
2008-03-10 0:59 ` Richard Scobie
2008-03-10 1:21 ` Michael Guntsche
2008-02-18 19:05 ` RAID5 to RAID6 reshape? Peter Grandi
2008-02-20 6:39 ` Alexander Kühn
2008-02-22 8:13 ` Peter Grandi
2008-02-23 20:40 ` Nagilum
2008-02-25 0:10 ` Peter Grandi
2008-02-25 16:31 ` Nagilum
2008-02-17 13:31 ` Janek Kozicki
2008-02-17 16:18 ` Conway S. Smith
2008-02-18 3:48 ` Neil Brown
2008-02-17 22:40 ` Mark Hahn
2008-02-17 23:54 ` Janek Kozicki
2008-02-18 12:46 ` Andre Noll
2008-02-18 18:23 ` Mark Hahn
2008-02-17 14:06 ` Janek Kozicki
2008-02-17 23:54 ` cat
2008-02-18 3:43 ` Neil 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=47BB63FF.3040202@rabbit.us \
--to=rabbit+list@rabbit.us \
--cc=janek_listy@wp.pl \
--cc=linux-raid@vger.kernel.org \
--cc=oliver.martin@student.tuwien.ac.at \
/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).