Hi Manuel,
I want to know more information about it. The points behind our calculations are these :
1. The capacity of Mosquitto broker is depending on the underlying OS and which in turn depends on what is maximum number of files (physical files or Network Sockets ) that OS can open concurrently. The maximum number of files that can be opened depends on what is the memory available for each process.
2. In linux the default value of max number of file open is 1024 and MQTT broker takes this value as its default. In order to set the max value beyond the 1024 , we need to change the linux settings for incr
easing the upper file limit.
3. The maximum value we can set on process level depending on how much memory is available on system for each process.
4. For each keep alive request memory conception is 16 bytes. Hence to keep 10k concurrent connection memory requirement is 160 MB and for 100k 1.6 GB
Now another important points are
1. we are opening the connection only based on the user activity. If user got notification, we are closing the connection.
2. So connection will not be open always.
3. Based on our understandings we can make more scalablility by introducing bridging of Mosquitto brokers
Please give me the answer for following questions :
1. At what point you couldn't able to support concurrent connections ? (Maximum limit of connection based on a specific configurations). ?
2. Is it correct that you are trying to support more than 100k connection using one mosquitto broker with the mentioned configuration ?
3. If possible please provide or tell me how will i get old archives of your mail, since i joined to the group recently.
Thanks & Regards
Jiji
