Software configuration

---

All servers were configured with Microsoft Windows 2000 and Sametime3.0, plus some fixes that will be available in Sametime 3.1.

Sametime MUX and Sametime Links SAs were installed on a single server because of the large number of servers needed to set up the test environment and the robot farm to simulate the large client load. The Sametime MUX is, by its nature as an I/O concentrator, CPU intensive but very low on memory requirements. On the other hand, the Sametime Links SA is written in Java and proxies thousands of Sametime Links clients and is, therefore, very memory intensive but not very high in CPU needs. These facts enabled us to install both processes on a single server, which we refer to as Sametime Links/MUX server.

Because the servers were dual CPU servers, we actually ran two separate Sametime Links server application processes, but only one Sametime MUX process because the Sametime MUX application needs to listen on a single port and it is not possible for two processes to listen to a single port on a single server. This enabled us to maximize the use of the server resources while still reaching the necessary level of scalability.

---