Open Stack

Joe,

There are a number of problem reports on ceilometer performance and some promising blueprints to address them. I'd suggest we re-run the performance test when those are in place. Having reference performance tests such as this are helpful to pick up cases where there are regression or scalability problems such as you raise (and production users see them also)

Tim

On 23 Apr 2014, at 18:51, Joe Gordon <joe.gordon0 at gmail.com<mailto:joe.gordon0 at gmail.com>> wrote:




On Mon, Apr 21, 2014 at 2:10 PM, Ilya Tyaptin <ityaptin at mirantis.com<mailto:ityaptin at mirantis.com>> wrote:
Hi team!

In light of discussions about ceilometer backends, we decided to test performance of different
storage backends with collector and api services because these services depend on backends availability.

For the collector testing we are using not completely real data, we are generating looking like real samples with variable rate, sending them to the collector and metering the time of these messages processing. Testing result is the time between message receiving for recording message to db.

For the api testing we are only comparing the time of requests to api with different backends.

We have prepared a document with more detailed description of test plan and first results.
This url: https://docs.google.com/document/d/1ARpKiYW2WN94JloG0prNcLjMeom-ySVhe8fvjXG_uRU/edit?usp=sharing

I am not sure if I read the 'Testing api' section correctly. Is that table in seconds?  If so a REST API that takes over two minutes (sample-list for Hbase, meter-list in Mongo) doesn't sound very good.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140423/be5bbf1b/attachment.html>