cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alena Prokharchyk <>
Subject Re: Should we have separate "Count" API?
Date Mon, 05 Nov 2012 23:43:47 GMT

We didn't use separate call as well as didn't use resource count table because we "count"
field represents the number of DB resources matching the search criteria (ignoring page/pageSize
info) specified in the list* api call. For example:


In the "count" field we expect to see the only how many vms in Running state, running on hostId=1
exist in the system; not the entire number of vms  in the system that we keep per account
in resource_count table.
And although only one vm object will be returned (as you requested page=1&pageSize=1),
you'll know how many vms in the system satisfy the search criteria.

As variation of parameters depends on particular API call, the count has to be returned as
a part of list* command response.


From: Min Chen <<>>
Reply-To: "<>"
To: "<>"
Subject: Should we have separate "Count" API?

Hi there,

In fixing the bug regarding count of a list API today, I cannot help wondering why we cannot
have separate "Count" api for such purpose rather than bundling this information with list
API, where we basically return some information that some users will just throw away since
they only care about count for dashboard purpose. I also noticed that in our DB schema, we
actually have a table "resource_count" there, not sure the original rational behind this table.
If we can take advantage of this table (and keep the information there up-to-date), we may
be able to provide a very efficient way to implement such "Count' apis for most commonly used
Any thoughts on this?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message