VMTurbo: Balance vs. Control: A Comparison
“How is VMTurbo different from any other tool that load balances through automated vMotions?” Anytime I am talking to a prospect on a demonstration, this question inevitably comes up in the conversation. VMTurbo often draws this comparison, and it comes down to a fundamental difference: the concept of balance versus control. Hopefully, this blog will elucidate the key difference between these two approaches to managing the virtual environment, and also how control assures application performance while also driving up utilization at the same time.
Load Balancing: One Mission and Only One Metric at a Time
With a load balancer in the environment, the administrator may believe that they are maintaining performance and keeping the environment healthy, because that is often how a load balancer is sold to them. Ultimately, however, a load balancer’s job is to do exactly what it is designed to do – balance the cluster through automated vMotions across a metric. When a load balancer looks at an environment, it attempts to move VM’s around within a cluster to balance either the metric of CPU or the metric of RAM on the hosts within that cluster. It considers one metric at a time, looking to achieve the most balanced state possible in regards to supply. Where it begins to fall short, however, is when we start to look at how balancing truly affects performance.
Read the entire article here, Balance vs. Control: A Comparison