If you intend to deploy one or more stand-alone Community Server multiplexers in front of a cluster of Community Servers, there are some issues to consider.
The stand-alone multiplexer maintains a single IP connection to each Community Server in the cluster. The data for all Community Server clients is transmitted over this single IP connection to the Community Server on the Sametime
® server. The illustration below shows stand-alone Community Services multiplexers deployed in front of clustered Community Servers to reduce the client connection load on the clustered servers.
In the illustration, note the following:
- The Community Server multiplexers are installed on separate computers and handle the connections from the clients.
- If you want to distribute connections among the multiplexers, you can set up a load-balancing mechanism such as IBM® Load Balancer.
- Each Community Server multiplexer maintains a single IP connection to Sametime server 1, and a single IP connection to Sametime server 2. The Community Server data is passed from the multiplexer computers to the Sametime Community Servers over these IP connections. Each Sametime Community Server maintains only two IP connections to handle all data.
- The scenario shown above can significantly increase the load-handling capabilities of the Sametime Community Servers. The table below illustrates the advantages of deploying stand-alone multiplexers.
| Multiplexer deployment || Number of Community Services connections |
| Two Sametime servers with the multiplexer installed on the same machines as the servers (default installation)||If the servers have multi-core processors, each Sametime Community Server can handle approximately 20,000 connections, for a total of 40,000 connections. Using the servers to host Sametime classic meetings rather than using Sametime meeting servers reduces the number of connections each server can support.|
| Two Sametime servers with the multiplexers installed on different computers (as seen in the illustration above) ||
- Each Sametime Community Server can service approximately 100,000 active connections.
- Each Community Server multiplexer machine can handle as many as 20,000 to 30,000 live IP port connections, for a possible total of 60,000 connections.
- The machines in the illustration above might be able to handle 160,000 active connections. You can increase the load handling capability further by adding additional Community Server multiplexers in front of the two Sametime Community Servers. For example, adding two more Community Server multiplexers to the cluster shown above might accommodate as many as 120,000 active connections (4 x 30,000 connections per Community Server multiplexer).
The server capacity numbers used above are approximations meant to provide a rough estimate of the possible load-handling improvement if you deploy Community Server multiplexers on separate computers. The actual server capacity is affected by variables such as:
- The average number of users in the contact lists of all Sametime clients
- The number of instant messages that users send
Server capacity is also reduced if you use Sametime
Classic meetings, which are legacy meetings hosted on a Sametime server, rather than using a Sametime Meeting server.
Parent topic: Deploying a stand-alone Community Server Mux