| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQTT client connection (to broker) limitation |
« View previous topic :: View next topic » |
| Author |
Message
|
| ivanachukapawn |
 Posted: Tue Aug 04, 2009 11:42 am Post subject: MQTT client connection (to broker) limitation |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
The broker information center displays this text:
A typical system might comprise several hundred client devices communicating with a single WebSphere Message Broker, where each client is identified by a unique ID. A single broker can manage a maximum of approximately 2000 clients.
This is in reference to MQTT client devices connected to a broker configured with SCADA nodes.
What is the basis for the 2000 client limitation? What studies were performed and on what equipment? |
|
| Back to top |
|
 |
| notox |
| Posted: Thu Jul 15, 2010 6:14 am Post subject: |
|
|
Newbie
Joined: 15 Jul 2010
Posts: 2
|
Does anyone have more information about the limitation of MQTT and some workarounds ?  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 15, 2010 6:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The picture is entirely different now.
Use the MQTT<->MQBridge. Review the documentation on that. Review what limits it does or doesn't have. |
|
| Back to top |
|
|
| notox |
| Posted: Thu Jul 15, 2010 7:56 am Post subject: |
|
|
Newbie
Joined: 15 Jul 2010
Posts: 2
|
thanks mqjeff, i tried but i got lost in an unknown world 
The thing is, i am done with what i wanted to do, i use a PHP server with SAM and MQTT, so i was wondering what would happen if for example 100 000 people were using my app, because i really don't know how much it can handle.. |
|
| Back to top |
|
|
| andypiper |
| Posted: Fri Dec 10, 2010 2:29 am Post subject: |
|
|
Acolyte
Joined: 29 Oct 2001
Posts: 59
Location: London
|
The limitation will be on the number of connections to the MQTT "server".
In WMB this was represented by the SCADAInput node which (I believe) topped out around a few thousand connections - I assume that number is from an earlier WMB version performance report. In the new WebSphere MQ Telemetry world, this is the Telemetry channel supported by the Telemetry service on the MQ Queue Manager, which has been tested to support significantly more connections, depending on platform and TCP/IP stack. Numbers are in the performance reports.
In terms of what will happen if too many users hit your client, I'm not sure what PHP/SAM scaled to, but generally you'd expect to start to get errors on your MQTT connections if the server was struggling to keep up, and you'd need to handle that in your PHP code. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
