Counting Sessions Is Not Enough
In a previous post I described a fundamental conceptual problem with load balancing, in particular as it applies to SBC. As I explained, load balancing is intended to provide optimal resource utilization, yet it is very difficult to provide a concrete, measurable definition of what ‘optimal’ means in this context. As a result, many administrators that actually test the functionality of the load balancing solution they utilize are content with simply verifying that sessions are evenly distributed between servers. For this reason Windows Server 2008 Terminal Services includes the Session Broker which provides exactly this type of distribution. Likewise, the default load evaluator in Citrix Presentation Server does essentially the same thing. However simple session distribution isnt necessarily the right thing to do, and it certainly isnt the only valid load distribution scheme as the following example demonstrates:
Consider a server farm comprised of identical servers, where each server is powerful enough to host 20 user sessions without any noticeable performance degradation. Now consider a load balancer that simply fills up servers to that capacity, one after another. That is it sends the first 20 users to the first server, the next 20 users to the second server and so on. An administrator testing solely for even session distribution will conclude that this load balancer is broken, because there would be up to 20 sessions on some servers and zero sessions on the others. Yet from the end-user perspective everything is working fine because each user is enjoying good performance.
Obviously the example above is simplistic, for example is doesn’t specify what happens after 20 sessions have been assigned to all the servers. Certainly we don’t use this method of load balancing in PowerTerm WebConnect. However, what it does exemplify is a load balancing scheme that contradicts conventional wisdom, yet can still be satisfactory. This example demonstrates why I consider even session distribution as a means, not an end. Moreover, in many cases it is not even a sufficient means, such as when some users require more resources than others. For this reason the default load balancing scheme employed by PowerTerm WebConnect does not rely solely on counting sessions. Instead the session count is just one of several criteria used to determine to which server a session will be assigned. Ill explain PowerTerm WebConnects default load balancing scheme in detail in an upcoming post so stay tuned.