This section discusses the performance advantages and procedures associated with deploying a stand-alone multiplexer in front of a Sametime
® server machine (or machines) that does not operate as part of a Community Server cluster.
server contains a Community Server multiplexer (or MUX) component. The function of the Community Server multiplexer is to handle and maintain connections from Sametime
clients to the Community Server.
During a normal Sametime
server installation, the Community Server multiplexer is installed with all other Sametime
components on the Sametime
server machine. The Sametime
server CD provides an option to install only the Community Server multiplexer component. This option enables the administrator to install the Community Server multiplexer on a different machine than the Sametime
When the Sametime
Community Server multiplexer is installed on a different machine than the Sametime
- The Sametime Connect clients connect to the Community Server multiplexer machine, not the Sametime server. This configuration frees the Sametime server from the burden of managing the live client connections; the multiplexer machine is dedicated to this task.
- The Community Server multiplexer maintains a single IP connection to the Sametime server. The data for all Community Server clients is transmitted over this single IP connection to the Community Server.
In this scenario, the Community Server connection-handling load is removed from the Sametime
server. The Sametime
server does not need to employ system resources to maintain thousands of client connections. Removing the connection-handling load from the Sametime
server ensures these system resources can be dedicated to other Community Server processing tasks.
The Community Server multiplexer machine dedicates its system resources to handling client connections but does not perform other Community Server processing. Distributing the Community Server workload between multiple servers in this way enables the Community Server to handle a larger number of connections (users) and to function more efficiently.
Performance improvements with a stand-alone multiplexer
If the Community Server multiplexer operates on the same machine as the Sametime
server, the Sametime
server can handle approximately 8,000 to 10,000 Community Server connections and also perform other Community Server processing tasks adequately.
However, if the Sametime
server is not required to expend system resources to maintain client connections, the server can service approximately 100,000 connections. (The Sametime
server is capable of processing the Community Server data that is passed over 100,000 connections if it does not have to maintain the connections themselves.)
When a Sametime
Community Server multiplexer is installed on a separate machine, the Community Server multiplexer can support approximately 20,000 live IP port connections. You can also deploy multiple Community Server multiplexers in front of a Sametime
To summarize the performance benefits of a stand-alone multiplexer deployment, consider the following example:
Parent topic: Deploying a stand-alone Community Server Mux
- You can install three separate Community Server multiplexers in front of a single Sametime server. If each Community Server multiplexer handles 20,000 connections, as many as 60,000 users can be connected to a single Sametime server at one time.
- If the Sametime server is capable of servicing 100,000 connections, the server performance will not degrade under the load produced by 60,000 connections.
- If the multiplexer operates on the Sametime server instead of being deployed separately, the Sametime server can service a maximum of 10,000 users. By deploying three stand-alone multiplexers in front of a single Sametime server, you can service 50,000 more users (assuming one connection per user) than if the multiplexer operates on the same machine as the Sametime server.
- If you deploy stand-alone multiplexers in the manner described above, you can also implement a rotating DNS system, or IBM® WebSphere® Edge Server, in front of the multiplexers to load balance connections to the stand-alone multiplexers.