Hi, I am forwarding this message (as suggested) to report a Proton issue. Thanks, MarcoF ---------- Forwarded message ---------- From: Fabio Lanari (Kiunsys) <fabio.lanari at kiunsys.com> Date: 2 February 2016 at 08:51 Subject: Fwd: RE: Opportunities for dissemination in FIWARE events To: Marco Fagiani <m.fagiani85 at gmail.com> Cc: Fabio Formosa <f.formosa at liberologico.com> La risposta di Telefonica. -------- Messaggio Inoltrato -------- Oggetto: RE: Opportunities for dissemination in FIWARE events Data: Mon, 1 Feb 2016 22:54:32 +0000 Mittente: SERGIO GARCIA GOMEZ <sergio.garciagomez at telefonica.com> <sergio.garciagomez at telefonica.com> A: Fabio Lanari (Kiunsys) <fabio.lanari at kiunsys.com> <fabio.lanari at kiunsys.com>, JOSE MANUEL CANTERA FONSECA <josemanuel.canterafonseca at telefonica.com> <josemanuel.canterafonseca at telefonica.com>, Paola Ponticelli <paola.ponticelli at kiunsys.com> <paola.ponticelli at kiunsys.com> CC: SANTIAGO MARTINEZ GARCIA <santiago.martinezgarcia at telefonica.com> <santiago.martinezgarcia at telefonica.com> Dear Fabio, The best way to handle this is to forward this message to fiware-tech-help at lists.fiware.org It’s better if you do it because you will get the email notifications on changes and answers. We will notify the Proton team anyway. Best Regards, Sergio. *De:* Fabio Lanari (Kiunsys) [mailto:fabio.lanari at kiunsys.com <fabio.lanari at kiunsys.com>] *Enviado el:* 01 February 2016 10:24 *Para:* JOSE MANUEL CANTERA FONSECA <josemanuel.canterafonseca at telefonica.com> <josemanuel.canterafonseca at telefonica.com>; Paola Ponticelli <paola.ponticelli at kiunsys.com> <paola.ponticelli at kiunsys.com> *CC:* SERGIO GARCIA GOMEZ <sergio.garciagomez at telefonica.com> <sergio.garciagomez at telefonica.com> *Asunto:* Re: Opportunities for dissemination in FIWARE events Hi Sergio, we have used these few days for performing one more test (VM scaling up). The main problem, as I said, is that Proton is consuming too much HW resources while managing only a bunch of alerting rules, which produces or the app crash or requires the VM restart. We have tested the entire system in 2 different IaaS installations. a) GEs used: IDAS IoT Agent 1.3.1. + ORION 0.26.1 + PROTON CEP 3.3.1 b) Installation type: local installation on a IaaS provider c) Installation method: Docker + Docker Compose Installations specs: - 1st installation: 1 VM (14 GB RAM, 4 core) containing the 3 GEs <-- in this case we haven' seen any problems. It should be said that this was an initial installation where we implemented only 2 or 3 Proton rules - 2nd installation - *small size* (due to IaaS provider migration): 1 VM (4 GB RAM, 2 core) containig the 3 GEs <-- in this case Proton eats up to 1.2 GB of RAM and constantly uses 98% of 2 cores (with 8 Proton rules) - 2nd installation - *mid-size* (scaling up of the previous VM): 1 VM (8 GB RAM, 4 core) containing the 3 GEs <-- Proton still eats up to 1.2 GB of RAM and constantly uses 3 cores at 100% (with 8 Proton rules) We don't know where the problem is. Our dev team thought there was too much messages between Orion and Proton, that Proton is unable to manage, so they are looking for a workaround, a method to reduce them. Here is the link to our bug/request: http://stackoverflow.com/questions/34491828/fiware-orion-context-broker-metadata-updates-trigger-notifications Thank you for your help Fabio L. -------- Messaggio originale -------- Oggetto: Re: Opportunities for dissemination in FIWARE events Mittente: JOSE MANUEL CANTERA FONSECA <josemanuel.canterafonseca at telefonica.com> <josemanuel.canterafonseca at telefonica.com> <josemanuel.canterafonseca at telefonica.com> A: Paola Ponticelli <paola.ponticelli at kiunsys.com> <paola.ponticelli at kiunsys.com> Data: 29/1/2016 10:13:56 Fabio, Paola, Please don’t forget to send us the ticket and some description about the problems found on your integration. Thanks, best -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20160205/c4b80d7f/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy