Session Manager Sizing

A given Session Manager instance allows large numbers of simultaneous client application connections.Each client application connection takes up a certain number of server resources such as CPU load, memory utilization, or network bandwidth.

Different types of client applications require different resources, such as CPU, memory, network bandwidth, and so on. For example, Interaction Supervisor requires different resources than the Interaction Desktop. Even different usages in the same client application type require different server resources, putting different loads on the Session Manager server. For example, a business user running the Interaction Desktop with the Company Directory and monitoring their own My Interactions tab, requires X resources, depending on how many people are in the Company Directory, how many interactions they receive, and other various factors. Consider a call center agent who has the Company Directory and a Workgroup Directory up, monitoring their My Interactions tab, as well as a workgroup Queue Statistics tab. That application usage could require vastly different resources than the application of a business user, depending on call volume, number of workgroups, and a vast number of additional variables.

Because of the impact of various client features on the performance requirements of Session Manager, there are certain guidelines for determining how many simultaneous user connections are appropriate for a given on-server or off-server Session Manager instance.By extension, this calculation also determines how many Session Manager instances are necessary for a given site.

Additionally, if regionalization is being used then the sizing calculation should be determined for each individual location.For more information, see Section 3.2 Sizing Calculation with Regionalization.