[openstack-dev] [Ceilometer] Sharing the load test result

Deok-June Yi june.yi at samsung.com
Mon Jan 6 00:14:58 UTC 2014

Hi, Ceilometer team.

I'm writing to share my load test result and ask you for advice about

Before starting, for whom doesn’t know Synaps [1], Synaps is
'monitoring as a service' project that provides AWS CloudWatch
compatible API. It was discussed to be merged with Ceilometer project
at Grizzly design phase, but Synaps developers could not join the
project for it at that time. And now Ceilometer has its own alarming

A few days ago, I installed Ceilometer and Synaps on my test
environment and ran load test for over 2 days to evaluate their
alarming feature in the aspect of real-time requirement. Here I attached
test environment diagram and test result. The load model was as below.
1.  Create 5,000 alarms
2.  [Every 1 minute] Create 5,000 samples

As a result, alarm evaluation time of Ceilometer was not predictable,
whereas Synaps evaluated all alarms within 2 seconds every minute.

This comes from two different design decisions for alarm evaluation
between Ceilometer and Synaps. Synaps does not read database but read
in-memory and in-stream data for alarming while Ceilometer involves
database read operations with REST API call.

I think Ceilometer is better to allow creating alarms with more complex
query on metrics. However Synaps is better if we have real-time
requirement with alarm evaluation.

So, how about re-opening the blueprint, cw-publish [2]?  It was
discussed and designed [3] at the start of Grizzly development cycle,
but it has not been implemented. And now I would like to work for it. Or
is there any good idea to fulfill the real-time requirement with

Please, don't hesitate in contacting me.

Thank you, 
June Yi

[1] https://wiki.openstack.org/Synaps
[2] https://blueprints.launchpad.net/ceilometer/+spec/cw-publish
[3] https://wiki.openstack.org/wiki/Ceilometer/blueprints/multi-publisher
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test_environment.png
Type: application/octet-stream
Size: 109353 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140106/ce4fc35b/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test_result.png
Type: application/octet-stream
Size: 67989 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140106/ce4fc35b/attachment-0003.obj>

More information about the OpenStack-dev mailing list