On Fri, Aug 10, 2007 at 10:57:50AM +0100, Richard W.M. Jones wrote:
> Daniel P. Berrange wrote:
> >The Xen implementations of
> >
> > virDomainLookupByID
> > virDomainLookupByUUID
> > virDomainLookupByName
> > virDomainGetOSType
> >
> >all have sub-optimal performance since they speak to Xe
On Fri, Aug 10, 2007 at 06:39:56AM -0400, Daniel Veillard wrote:
> On Thu, Aug 09, 2007 at 11:13:00PM +0100, Daniel P. Berrange wrote:
> > The Xen implementations of
> >
> >virDomainLookupByID
> >virDomainLookupByUUID
> >virDomainLookupByName
> >virDomainGetOSType
> >
> > all have
On Fri, Aug 10, 2007 at 02:33:28PM +0100, Daniel P. Berrange wrote:
> On Fri, Aug 10, 2007 at 06:39:56AM -0400, Daniel Veillard wrote:
> > Well if you have 100 guests, that may be slower, but in the average
> > situation
> > of only a couple of guests, it could be a real speedup. The problem is
On Thu, Aug 09, 2007 at 11:13:00PM +0100, Daniel P. Berrange wrote:
> The Xen implementations of
>
>virDomainLookupByID
>virDomainLookupByUUID
>virDomainLookupByName
>virDomainGetOSType
>
> all have sub-optimal performance since they speak to XenD. The lookupXXX
> functions all ba
Daniel P. Berrange wrote:
The Xen implementations of
virDomainLookupByID
virDomainLookupByUUID
virDomainLookupByName
virDomainGetOSType
all have sub-optimal performance since they speak to XenD. The lookupXXX
functions all basically require 3 pieces of info in the end (name,id,uuid)
The Xen implementations of
virDomainLookupByID
virDomainLookupByUUID
virDomainLookupByName
virDomainGetOSType
all have sub-optimal performance since they speak to XenD. The lookupXXX
functions all basically require 3 pieces of info in the end (name,id,uuid).
They each get given one pi
