incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Itamar Heim" <ih...@redhat.com>
Subject RE: [rhevm-api] [jira] [Commented] (DTACLOUD-58) api/instance query performance with 8 vms in rhevm
Date Thu, 14 Jul 2011 19:20:47 GMT


> -----Original Message-----
> From: rhevm-api-bounces@lists.fedorahosted.org
[mailto:rhevm-api-bounces@lists.fedorahosted.org] On
> Behalf Of David Lutterkort
> Sent: Thursday, July 14, 2011 20:46 PM
> To: deltacloud-dev@incubator.apache.org
> Cc: rhevm-api@lists.fedorahosted.org; 'Mark McLoughlin'; 'Chris
Lalancette'
> Subject: Re: [rhevm-api] [jira] [Commented] (DTACLOUD-58) api/instance
query performance with 8 vms in
> rhevm
> 
> On Thu, 2011-07-14 at 10:52 -0400, Itamar Heim wrote:
> > Your use case is more close to backend --> vdsm, where we poll every 2
> > seconds actually.
> > But the polling every 2 seconds is a very light poll - only list of
VM's
> > and their status.
> > The heavier polling for all detils/stats is not as frequent.
> >
> > So you should probably define the minimal data you need to poll for
more
> > frequently, and run the lighter query (the api has a 'detail' level,
> > though probably not one that light yet).
> 
> Do you have any data on what details they are and how often Powershell
> can support listing all instances at that detail level ?

I didn't say we have that detail level yet in REST, and powershell for
sure doesn't have that optimization.
but we should plan ahead for such a lightweight query on status of VMs, so
the question is do you need anything but vm_id and vm_status for such a
query?
Einav - would we need more things for a lightweight user portal query?

Mime
View raw message