-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IoT Agent LWM2M Memory exhaust and production environment #88
Comments
Hi Secmotic, Could you please paste your config.js file ? |
Hello @fermenreq , Thanks for your answer. We have been testing with different config files. This one in particular has a prototype of device that we are using, but we have tested with several, including and not including the device (so we would discard that as a problem). We actually noticed that the problem is the CPU managing and the number of requests between Orion Context Broker and the IOTA. In our case, the simple request of the subscription is a large one, and when connecting approximately 250 devices with no data transfer, the CPU reachs about 60%. This is a problem, since a simple requests to a group of devices can block the system...
|
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.
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?
Thanks in advance
The text was updated successfully, but these errors were encountered: