All of lore.kernel.org
 help / color / mirror / Atom feed
From: Syed Mushtaq <syed1.mushtaq@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: Tim Mackey <Timothy.Mackey@citrix.com>,
	Will Stevens <wstevens@cloudops.com>,
	"Tutkowski, Mike" <Mike.Tutkowski@netapp.com>,
	Pierre-Luc Dion <pdion@cloudops.com>,
	Marc Vaillancourt <mvaillancourt@cloudops.com>
Subject: LVM performance problems with large number of VGs
Date: Fri, 1 Apr 2016 10:23:42 -0400	[thread overview]
Message-ID: <CADMzvUpzD6bz2hzF+Ji+cTUBhxAWKC2j9mJ32t9UQXGM3W4k4Q@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]

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.

Thanks,
-Syed

[-- Attachment #1.2: Type: text/html, Size: 978 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

             reply	other threads:[~2016-04-01 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 14:23 Syed Mushtaq [this message]
2016-04-01 15:22 ` LVM performance problems with large number of VGs Wei Liu
2016-04-01 15:53   ` Syed Mushtaq
2016-04-01 16:38 ` Roger Pau Monné
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=CADMzvUpzD6bz2hzF+Ji+cTUBhxAWKC2j9mJ32t9UQXGM3W4k4Q@mail.gmail.com \
    --to=syed1.mushtaq@gmail.com \
    --cc=Mike.Tutkowski@netapp.com \
    --cc=Timothy.Mackey@citrix.com \
    --cc=mvaillancourt@cloudops.com \
    --cc=pdion@cloudops.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.