incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Lalancette <clala...@redhat.com>
Subject Re: [jira] [Commented] (DTACLOUD-58) api/instance query performance with 8 vms in rhevm
Date Thu, 14 Jul 2011 12:49:59 GMT
On 07/14/11 - 10:17:03AM, Mark McLoughlin wrote:
> On Thu, 2011-07-14 at 09:53 +0200, Michal Fojtik wrote:
> > On Jul 14, 2011, at 12:16 AM, David Lutterkort (JIRA) wrote:
> > 
> > > 
> > >    [ https://issues.apache.org/jira/browse/DTACLOUD-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064913#comment-13064913
] 
> > > 
> > > David Lutterkort commented on DTACLOUD-58:
> > > ------------------------------------------
> > > 
> > > The 'heartbeat' isn't coming from deltacloud, but from aeolus; 
> > > reloading the list of all VM's every 30s is way too often.
> 
> This isn't what I expected actually
> 
> In aeolus, condor is what's monitoring running instances and I thought
> it did that be GETing each instance individually every 90 seconds

No, condor does a batch update of every provider every 30 seconds.  We can
certainly tune that down, but the problem is that it is a tradeoff; the longer
the timeout, the worse the user experience becomes in terms of updating the
UI with the current state.  Even with the 30 second timeout, we are getting
complaints that we take "way longer" to show an instance going to running
than the EC2 front-end.

-- 
Chris Lalancette

Mime
View raw message