From: Lars Ellenberg <linux-lvm@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Re: LVM Performance effects?
Date: Thu, 13 Jul 2006 19:43:31 +0200 [thread overview]
Message-ID: <20060713174331.GF4093@soda.linbit> (raw)
In-Reply-To: <44B66D47.4000001@designassembly.de>
/ 2006-07-13 17:56:55 +0200
\ Michael Heyse:
> (sorry for disrupting the thread - copied this message from the archives)
>
> > I have set up a file server with LVM on top of RAID 5, and seem to be
> > having LVM related performance issue.
>
> Me too.
>
> > raid device: 118.2 MB/s
> > lvm device: 49.43 MB/s
> > file system: 40.83 MB/s
>
> Have you found an answer to that problem? I couldn't find anything
> helpful in the archives. Is this a general LVM on software RAID issue?
maybe lvm (device mapper) does not propagate the read-ahead
parameters of the physical device to the upper layers
(we had a similar problem with drbd, which in respect to this problem is
"just an other" virtual block device)
once we did (block device kernel code during device creation)
+
+ if( q->backing_dev_info.ra_pages != b->backing_dev_info.ra_pages) {
+ INFO("Adjusting my ra_pages to backing device's (%lu -> %lu)\n",
+ q->backing_dev_info.ra_pages,
+ b->backing_dev_info.ra_pages);
+ q->backing_dev_info.ra_pages = b->backing_dev_info.ra_pages;
+ }
+
we suddenly got basically all the bandwidth the box could deliver.
without that patch and that particular storage backend we had only
about 1/6 of the performance.
other storage backends don't care at all.
you could verify this with "blockdev --getra /dev/whatever",
and try to tune it with "blockdev --setra 1024 /dev/whatever".
--
: Lars Ellenberg Tel +43-1-8178292-0 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com :
prev parent reply other threads:[~2006-07-13 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 15:56 [linux-lvm] Re: LVM Performance effects? Michael Heyse
2006-07-13 17:43 ` Lars Ellenberg [this message]
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=20060713174331.GF4093@soda.linbit \
--to=linux-lvm@linbit.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).