You’ve decided that you want to try out V-locity® software – kick the tires so to speak. You’ll just load it on one of your Virtual Machines and see how it goes. What kind of benefit will you see?
It is true that V-locity will likely provide significant benefit on that one VM. It may even be extraordinary. But loading V-locity on just one VM on a host with sometimes dozens of VMs won’t give you the biggest bang for your buck. V-locity includes many technologies that address storage performance issues in an extremely intelligent manner. Part of the underlying design is to learn about the specific loads your system has and intelligently adapt to each specific environment presented to it. That’s why we created a product especially for Virtual environments in the first place.
The beauty of V-locity is its ability to deal with something called the I/O Blender Effect. This is the dark side of virtualized systems. When there are multiple VMs on a host, or multiple hosts with VMs that use the same back-end storage system (e.g., a SAN) a “blender” effect occurs when all these VMs are sending I/O requests up and down the stack. As you can guess, it can create huge performance bottlenecks. In fact, perhaps the most significant issue that virtualized environments face is the fact that there are MANY performance chokepoints in the ecosystem, especially the storage subsystem. These chokepoints are robbing 30-50% of your throughput. That’s what V-locity can recover.
Look at it this way. VM “A” may have different resource requirements than VM “B” and so on. Besides performing different tasks with different workloads, they may have different peak usage periods. What happens when those peaks overlap? Worse yet, what happens if several of your VMs have very similar resource requirements and workloads that constantly overlap?
The answer is that the I/O Blender Effect takes over and now VM “A” is competing directly with VM “B” and VM “C” and so on. The blender pours all those resource desires into a funnel, creating bottlenecks with unpredictable performance results. What is predictable is that performance will suffer, and likely a LOT.
Enter V-locity. V-locity was designed from the ground up to intelligently deal with these core issues. The guiding question in front of us as it was being designed and engineered, was:
Given your workload and resources, how can V-locity help you overcome the I/O Blender Effect?
By making sure that V-locity will adapt to your specific workload and having studied what kinds of I/Os amplify the I/O Blender Effect, we were able to add intelligence to specifically go after those I/Os. We take a global view. We aren’t limited to a specific application or workload. While we do have technologies that shine under certain workloads, such as transactional SQL applications, our goal is to optimize the entire ecosystem. That’s the only way to overcome the I/O Blender Effect.
So, while we can indeed give you great gains on a single VM, V-locity truly gets to shine and show off its purpose when it can intelligently deal with the chokepoints that create the I/O Blender Effect. That means you should add V-locity to ALL your VMs. With our no-reboot installation and a V-locity Management Console, it’s fast and easy to cover and manage your environment.
And yes, this same I/O Blender effect can occur in your physical environment with multiple physical systems all accessing different LUNs on the same SAN. Our Diskeeper® software is the answer here.
Go ahead and try V-locity on the VMs that are in the most competition for resources and you’ll be amazed at the benefits. The chokepoints aren’t obvious or right in front of your face, but they are real and V-locity is the answer. After that, just add V-locity to all your VMs, then sit back and see how smart you were to so easily improve throughput across your eco-system.