All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Syed Mushtaq <syed1.mushtaq@gmail.com>
Cc: "Tutkowski, Mike" <Mike.Tutkowski@netapp.com>,
	Will Stevens <wstevens@cloudops.com>,
	Marc Vaillancourt <mvaillancourt@cloudops.com>,
	Pierre-Luc Dion <pdion@cloudops.com>,
	xen-devel@lists.xenproject.org,
	Tim Mackey <Timothy.Mackey@citrix.com>
Subject: Re: LVM performance problems with large number of VGs
Date: Fri, 1 Apr 2016 18:38:36 +0200	[thread overview]
Message-ID: <alpine.OSX.2.20.1604011836350.9476@mac> (raw)
In-Reply-To: <CADMzvUpzD6bz2hzF+Ji+cTUBhxAWKC2j9mJ32t9UQXGM3W4k4Q@mail.gmail.com>

On Fri, 1 Apr 2016, Syed Mushtaq wrote:
> Hi,
> 
> I am testing out a system in which each Guest disk is mapped to a LUN on a backend storage. I am using Xenserver 6.5 for this and creating an SR with a single VDI inside it for each Guest disk.
> The way it would work is, from an LVM point of view, I would have a Volume Group (VG) for each virtual disk and a single logical volume (LV) inside that VG. What I am seeing is that creating new
> volume groups is taking a lot of time. In my test after creating about 600 volume groups, it took about 4 seconds to create a new one. I have observed this to be a linear trend where the more
> VGs I add the slower future operations become. Other operations like getting the logical volumes inside a VG have also slowed down (even though there is only 1 LV per VG).
> 
> I was wondering if anyone here faced a similar problem or had some experience in dealing with LVM bottlenecks.

It doesn't seem like this is related to Xen, so I would recommend that you 
ask in the linux-lvm [0] mailing list. TBH, I have no idea how well LVM 
scales in these kind of scenarios.

Roger.

[0] https://www.redhat.com/mailman/listinfo/linux-lvm

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-04-01 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 14:23 LVM performance problems with large number of VGs Syed Mushtaq
2016-04-01 15:22 ` Wei Liu
2016-04-01 15:53   ` Syed Mushtaq
2016-04-01 16:38 ` Roger Pau Monné [this message]
2016-04-01 17:19   ` Syed Mushtaq

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=alpine.OSX.2.20.1604011836350.9476@mac \
    --to=roger.pau@citrix.com \
    --cc=Mike.Tutkowski@netapp.com \
    --cc=Timothy.Mackey@citrix.com \
    --cc=mvaillancourt@cloudops.com \
    --cc=pdion@cloudops.com \
    --cc=syed1.mushtaq@gmail.com \
    --cc=wstevens@cloudops.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.