From: Zdenek Kabelac <zkabelac@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Thin Pool Performance
Date: Tue, 19 Apr 2016 10:11:25 +0200 [thread overview]
Message-ID: <5715E82D.1070300@redhat.com> (raw)
In-Reply-To: <CAO_L6qEOfivZ2PwJEzNFWnuECikZb8HqOX2Hn9DigMC62WSgqA@mail.gmail.com>
Dne 19.4.2016 v 03:05 shankha napsal(a):
> Hi,
> Please allow me to describe our setup.
>
> 1) 8 SSDS with a raid5 on top of it. Let us call the raid device : dev_raid5
> 2) We create a Volume Group on dev_raid5
> 3) We create a thin pool occupying 100% of the volume group.
>
> We performed some experiments.
>
> Our random write operations dropped by half and there was significant
> reduction for
> other operations(sequential read, sequential write, random reads) as
> well compared to native raid5
>
> If you wish I can share the data with you.
>
> We then changed our configuration from one POOL to 4 POOLS and were able to
> get back to 80% of the performance (compared to native raid5).
>
> To us it seems that the lvm metadata operations are the bottleneck.
>
> Do you have any suggestions on how to get back the performance with lvm ?
>
> LVM version: 2.02.130(2)-RHEL7 (2015-12-01)
> Library version: 1.02.107-RHEL7 (2015-12-01)
>
Hi
Thanks for playing with thin-pool, however your report is largely incomplete.
We do not see you actual VG setup.
Please attach 'vgs/lvs' i.e. thin-pool zeroing (if you don't need it keep it
disabled), chunk size (use bigger chunks if you do not need snapshots), number
of simultaneously active thin volumes in single thin-pool (running hundreds of
loaded thinLV is going to loose battle on locking) , size of thin pool
metadata LV - is this LV located on separate device (you should not use RAID5
with metatadata)
and what kind of workload you try on ?
Regards
Zdenek
next prev parent reply other threads:[~2016-04-19 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 1:05 [linux-lvm] Thin Pool Performance shankha
2016-04-19 8:11 ` Zdenek Kabelac [this message]
2016-04-20 13:34 ` shankha
2016-04-20 15:55 ` shankha
2016-04-20 19:50 ` shankha
2016-04-28 10:20 ` Marian Csontos
2016-04-29 15:37 ` shankha
2016-04-26 17:38 ` Linda A. Walsh
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=5715E82D.1070300@redhat.com \
--to=zkabelac@redhat.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.