My test involved 200k clients subscribed to 1 of 10 topics and publishing on the random interval of 0 to 1800 seconds to one of the 10 topics. Everything was done at QoS 2, SSL off.
An easy workaround that we've taken is to encrypt the payload over the non-secure connection. The burden is then placed on the message producing/consuming software but that's something that just has to be dealt with when maintaining so many open connections. - Mike -----Original Message----- From: mosquitto-users-bounces+michael.frisch=nuance....@lists.launchpad.net [mailto:mosquitto-users-bounces+michael.frisch=nuance....@lists.launchpad.net] On Behalf Of Roger Light Sent: Wednesday, November 14, 2012 12:36 PM To: mosquitto-users@lists.launchpad.net Subject: Re: [Mosquitto-users] Build up a MQTT server with about 20, 000+ subscribers Hi Mike, > - There’s not much special, EC2 mediums can do 200k+ (yes, two > hundred) with QoS 2, SSL off, and a moderate number of messages > publishing constantly. Can you offer any further details on what "moderate" means here? Just a rough order of magnitude would be nice to know. > Sharon, the problem that I can already tell you that will arise with > SSL is memory usage. I forget the exact numbers but calling the > consumption noticeable would be an understatement. With SSL off > Mosquitto uses such a small amount of RAM which is why EC2 high CPU mediums > are perfect. Yes... It would be nice to try something less heavyweight than openssl, but the nice obvious alternatives like cyassl are gpl/commercial licensed. Cheers, Roger -- Mailing list: https://launchpad.net/~mosquitto-users Post to : mosquitto-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~mosquitto-users More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~mosquitto-users Post to : mosquitto-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~mosquitto-users More help : https://help.launchpad.net/ListHelp