cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remi Bergsma <>
Subject Re: [jira] dsclose mentioned you (JIRA)
Date Fri, 03 Jun 2016 20:34:08 GMT

The sorting I did was in JavaScript on the UI so that's probably not it as you see it in the
API, right?

Can you check if the database load is spiking during these calls? Sounds like an index problem
or so. 

Regards, Remi 

Sent from my iPhone

> On 03 Jun 2016, at 13:23, dsclose (JIRA) <> wrote:
>     [
> dsclose mentioned you on CLOUDSTACK-9405
> --------------------------------
> We recently upgraded from Cloudstack 4.5.2 to Cloudstack 4.8.0. Since this update, the
listDomains API call has started taking an extremely long time to respond. This has caused
issues with our services that rely on this API call. Initially they simply timed out until
we increased the thresholds. Now we have processes that used to take a few seconds taking
many minutes.
> This is so problematic for us that our organisation has put a halt on further updates
of Cloudstack 4.5.2 installations. If reversing the update of zones already on 4.8.0 was feasible,
we would have reverted back to 4.5.2.
> Here is a table of the times we're seeing:
> ||CS Version||Domain Count||API Response Time||
> |4.5.2|251|~3s|
> |4.8.0|182|~26s|
> |4.8.0|<10|<1s|
> This small data sample indicates that the response time for zones with a larger amount
of domains is significantly worse after the update to 4.8.0. Zones with few domains aren't
able to reproduce this issue.
> I recall a bug being resolved recently that concerned reducing the response time for
list* API calls. I also recall [~remibergsma] resolving a bug concerning the sorting of the
listDomains response. Is it possible that these issues are connected?
>>                Key: CLOUDSTACK-9405
>>        View Online:
>>        Add Comment:
> Hint: You can mention someone in an issue description or comment by typing  "@" in front
of their username.
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)

View raw message