monasca team mailing list archive

["Brandt, Ryan" <ryan.brandt@xxxxxxx>]

Hello Tomasz,
There was some local testing for sending metrics to the API and verifying when they are available in the metrics database. The tests showed the two APIs are close in performance, however I do not have any exact results on hand.

As for alarms, from general observation in devstack and mini-mon, an alarm should appear within a few seconds of the metric being submitted. If this is not the case, a good first step is to check that all monasca components are running without errors in the logs and the alarm definition expression and match by fields fit the metric being submitted.

Ryan Brandt

From: Monasca <monasca-bounces+ryan.brandt=hp.com@xxxxxxxxxxxxxxxxxxx<mailto:monasca-bounces+ryan.brandt=hp.com@xxxxxxxxxxxxxxxxxxx>> on behalf of "Tomasz.Trebski@xxxxxxxxxxxxxx<mailto:Tomasz.Trebski@xxxxxxxxxxxxxx>" <Tomasz.Trebski@xxxxxxxxxxxxxx<mailto:Tomasz.Trebski@xxxxxxxxxxxxxx>>
Date: Tuesday, December 22, 2015 at 5:00 AM
To: "monasca@xxxxxxxxxxxxxxxxxxx<mailto:monasca@xxxxxxxxxxxxxxxxxxx>" <monasca@xxxxxxxxxxxxxxxxxxx<mailto:monasca@xxxxxxxxxxxxxxxxxxx>>
Subject: [Monasca] Performance comparison between Java/Python implementation for monasca-api

Hello monasca,

I wanted to ask if you, by chance, happened to perform performance comparison between
Java and Python implementation of monasca-api ?
If so, are there results available anywhere ? Also, could you share any approaches you have been
taking to verify it or have you conducted those isolated only for monasca-api or for entire
system – looking how long it takes for metric to transform into an alarm ?

Tomasz Trębski

R&D Development Engineer / EST
Łódź GDC
[cid:image001.gif@01CF78FC.4ACD6460]
FUJITSU
Textorial Park, ul. Fabryczna 17
90-344 Łódź, Poland
Mob.: +48 789 231 312
E-mail: tomasz.trebski@xxxxxxxxxxxxxx<mailto:tomasz.trebski@xxxxxxxxxxxxxx>
Web: ts.fujitsu.com<http://ts.fujitsu.com/>
Company details: pl.ts.fujitsu.com/imprint<http://pl.ts.fujitsu.com/imprint.html>
This communication contains information that is confidential, proprietary in nature and/or privileged.  It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) or the person responsible for delivering it to the intended recipient(s), please note that any form of dissemination, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender and delete the original communication. Thank you for your cooperation.
Please be advised that neither Fujitsu, its affiliates, its employees or agents accept liability for any errors, omissions or damages caused by delays of receipt or by any virus infection in this message or its attachments, or which may otherwise arise as a result of this e-mail transmission.

Attachment: image001.gif
Description: image001.gif