What is the largest number of Clients that are allowed to connect to one RTServer?
Article ID: KB0087561
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
In SmartSockets version 6.6 and greater RTserver is allowed to use as many file descriptors as the process is allowed by the OS. Note: In UNIX systems this is settable using the limits command. In previous releases the number of RTclients that could connect to a single RTserver was limited by the number of file descriptors that could be added to a select mask, generally ~1024 simultaneous descriptors.
That being said, other factors weigh in regarding a realistic upper limit on the number of connections RTserver can hold at any given time.
1). The RTserver option Max_Client_Conns (this is a hard limit) specifies the maximum number of RTclient processes that are allowed to connect to the RTserver. If this limit is exceeded, no more RTclients are allowed to connect. The default value of this option is 200.
2). Holding a large number of connections maybe more attainable in situations where the RTclients are not very transient, in other words, once connected they stay connected for a long period of time as oppossed to high levels of RTclient connect/disconnects.
3). Observation suggests that the message rate not exceed ~15000 msgs per second for a long period of time.
4). Avoid large subject space (each RTclient subscribing to thousands of subjects puts added strain on RTserver).
5). Hardware limitation (CPU/memory), network bandwidth, RTserver trace logging to file, using GMD, all potentially affect the performance of the RTserver.
In SmartSockets version 6.6 and greater RTserver is allowed to use as many file descriptors as the process is allowed by the OS. Note: In UNIX systems this is settable using the limits command. In previous releases the number of RTclients that could connect to a single RTserver was limited by the number of file descriptors that could be added to a select mask, generally ~1024 simultaneous descriptors.
That being said, other factors weigh in regarding a realistic upper limit on the number of connections RTserver can hold at any given time.
1). The RTserver option Max_Client_Conns (this is a hard limit) specifies the maximum number of RTclient processes that are allowed to connect to the RTserver. If this limit is exceeded, no more RTclients are allowed to connect. The default value of this option is 200.
2). Holding a large number of connections maybe more attainable in situations where the RTclients are not very transient, in other words, once connected they stay connected for a long period of time as oppossed to high levels of RTclient connect/disconnects.
3). Observation suggests that the message rate not exceed ~15000 msgs per second for a long period of time.
4). Avoid large subject space (each RTclient subscribing to thousands of subjects puts added strain on RTserver).
5). Hardware limitation (CPU/memory), network bandwidth, RTserver trace logging to file, using GMD, all potentially affect the performance of the RTserver.
Issue/Introduction
What is the largest number of Clients that are allowed to connect to one RTServer?
Feedback
Yes
No
Powered by
