[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Working around xenstored performance?


  • To: Pim van Riezen <pi+lists@xxxxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 31 Jul 2008 09:43:44 +0100
  • Cc:
  • Delivery-date: Thu, 31 Jul 2008 01:44:16 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acjy6YozyOgltF7cEd2L3gAX8io7RQ==
  • Thread-topic: [Xen-devel] Working around xenstored performance?

If you can run as root on the box you can make a libxenctrl call yourself to
xc_domain_getinfo() or xc_domain_getinfolist().

 -- Keir

On 31/7/08 09:41, "Pim van Riezen" <pi+lists@xxxxxxxxxxxx> wrote:

> Good Day,
> 
> For monitoring purposes, we have a process that sends a 'xend.domains'
> methodCall to xend at timed intervals. Our problem here is that this
> call, if the extra parameter is not '0', is pretty slow; xenstored
> will run with 40% cpu grinding over its database before coming up with
> a reply, hardly something you want to do like every 15 seconds. With
> the parameter on 0, the response is instantaneous, but lacks any
> information beyond the list of currently running guests.
> 
> Is there a less intrusive way to just get the cpu-counter for a
> specific guest through /proc/xen or some such? I'd also be perfectly
> happy to fish the information out of xenstored's tdb-file, but all of
> its records seem to be in an undocumented binary encoding so that's
> not really helping either.
> 
> Our set-up is the Fedora branch of 3.0 (but from what I can read, 3.1
> still has this problem).
> 
> Cheers,
> Pim van Riezen
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.