From: Chris Cox <chris_cox@stercomm.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM Overhead
Date: Mon, 24 Sep 2007 11:39:21 -0500 [thread overview]
Message-ID: <46F7E839.8040805@stercomm.com> (raw)
In-Reply-To: <46F7E720.4060304@stercomm.com>
Chris Cox wrote:
> Tomasz Chmielewski wrote:
>> Chris Cox schrieb:
>>> Joseph L. Casale wrote:
>>>> Hi,
>>>> I am wanting to use LVM behind an iet iscsi target and I am wondering
>>>> how much overhead if any does LVM add? Would the performance degrade
>>>> any, currently I am exporting full unpartitioned discs and am happy with
>>>> the performance. From what I am reading now, I would likely partition
>>>> the physical discs and use that in LVM then export a volume.
>>> Overhead is negligible. I haven't seen any impact at all.
>> Quite the contrary - unless the default settings are not changed.
>>
>>
>> By default, the readahead values for LVM volumes is quite low / for
>> iSCSI, I always have to change it to get acceptable performance (one
>> might want to replace the $HOSTNAME with the name of the PV, or define a
>> separate list; "setra" values might need some experimenting, too):
>>
>>
>> LVMS=$(/bin/ls /dev/$HOSTNAME/)
>>
>> for LVM in $LVMS
>> do
>> blockdev --setra 16384 /dev/$HOSTNAME/$LVM
>> done
>>
>>
>
> Hmmm, perhaps for iSCSI. But using fibre SAN, I saturate my
> 2Gbps link (almost 200MB/sec).
>
>
I check my local drives, they all use the default 1024....
Is setting the read ahead that big of a deal with just LVM?
I would think if it's an issue, it's an issue everywhere.
--
Chris Cox
Sr. Unix Sys Admin
next prev parent reply other threads:[~2007-09-24 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 18:25 [linux-lvm] LVM Overhead Joseph L. Casale
2007-09-24 15:05 ` Chris Cox
2007-09-24 15:15 ` Tomasz Chmielewski
2007-09-24 16:34 ` Chris Cox
2007-09-24 16:39 ` Chris Cox [this message]
2007-09-24 17:52 ` Tomasz Chmielewski
2007-09-25 15:13 ` Chris Cox
2007-09-24 18:04 ` Joseph L. Casale
2007-09-26 16:10 ` Chris Cox
2007-09-26 16:59 ` Joseph L. Casale
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=46F7E839.8040805@stercomm.com \
--to=chris_cox@stercomm.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 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.