[ https://jira.fiware.org/browse/HELP-12626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] FW External User updated HELP-12626: ------------------------------------ Attachment: Jose3.png Comment by jose at secmotic.com : Thanks a lot Stefano, Just one thing, the GE tested is IDAS Iot Agent, but it doesn't specify which one of the Agents have been tested. These results seems pretty good and they are similar to our results for the Ultralight 2.0 agent, but we are facing a complete different scenario with the LWM2M IoT Agent (in its last version). The CPU in the LWM2M reaches the 100% of usage for the same inputs that in the report (but with larger json in the requests). Is it possible that the results are different from one IoT Agent to another? Best regards -- Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. > El 31 ago 2017, a las 15:13, Help-Desk <jira-help-desk at jira.fiware.org> escribió: > > > > [Fiware-tech-help] Unresolved question stackoverflow: IoT Agent LWM2M Memory exhaust and production environment > --------------------------------------------------------------------------------------------------------------- > > Key: HELP-12626 > URL: https://jira.fiware.org/browse/HELP-12626 > Project: Help-Desk > Issue Type: extRequest > Components: FIWARE-TECH-HELP > Reporter: FW External User > Assignee: Stefano De Panfilis > Attachments: Jose3.png, Jose3.png, Jose3.png > > > Hello. Can anyone give some insights to this question? > IoT Agent LWM2M Memory exhaust and production environment <https://stackoverflow.com/questions/45172339/iot-agent-lwm2m-memory-exhaust-and-production-environment> > I'm working on a project which aims to connect +1k devices to a machine, which may probably autoscale. The problem is that with only 2 connected devices, the IDAS IoTAgent ends in a couple of days with a "Memory exhaust" message. It is running in a docker instance in a machine in AWS m3.medium with memory swap. > On the other hand, the git repository is not longer maintained as far as I can see, since there are not commits since Dec 16'. Is this a recomendable Generic Enabler for production? Has it been tested for a big amount of connected devices? Is this actually out of maintenance? > Here it is the url to the git repo: > https://github.com/telefonicaid/lightweightm2m-iotagent <https://github.com/telefonicaid/lightweightm2m-iotagent> > Thanks in advance > -- > Confidentiality notice: > This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. > __________________________________________________________________________________________ > You can get more information about our cookies and privacy policies on the following links: > - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy > - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE > Fiware-tech-help mailing list > Fiware-tech-help at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-tech-help > [Created via e-mail received from: Jose Benitez <jose at secmotic.com>] -- This message was sent by Atlassian JIRA (v6.4.1#64016)
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy