Virtualization: Tips for avoiding server overload

As virtualization stretches deeper into the enterprise to include mission-critical and resource-intensive applications, IT executives are learning that double-digit physical-to-virtual server ratios are things of the past.

Virtualization vendors may still be touting the potential of putting 20, 50, or even 100 VMs (virtual machines) on a single physical machine, but IT managers and industry experts say those ratios are dangerous in production environments, causing performance problems or, worse, outages.

"In test and development environments, companies could put upwards of 50 virtual machines on a single physical host. But when it comes to mission-critical and resource-intensive applications, that number tends to plummet to less than 15," says Andi Mann, vice president of research at Enterprise Management Associates (EMA) in Boulder, Colo.

In fact, EMA conducted a study in January 2009 of 153 organizations with more than 500 end users and found that on average they were achieving 6:1 consolidation rates for applications such as ERP, CRM, e-mail and database.

The variance between the reality and the expectations, whether it's due to vendor hype or internal ROI issues, could spell trouble for IT teams. That's because the consolidation rate affects just about every aspect of a virtualization project: budget, capacity and executive buy-in. "If you go into these virtualization projects with a false expectation, you're going to get in trouble," Mann says.

Indeed, overestimating P-to-V ratios can result in the need for more server hardware, power consumption, heating and cooling, and rack space -- all of which cost money. Worse yet, users could be impacted by poorly performing applications. "If a company thinks they're only going to need 10 servers at the end of a virtualization project and they actually need 15, it could have a significant impact on the overall cost of the consolidation and put them in the hole financially. Not a good thing, especially in this economy," says Charles King, president and principal analyst at consultancy Pund-IT in Hayward, Calif.

Key apps will fight for server space

So, why the disconnect between virtualization expectations and reality? King says up to this point, many companies have focused on virtualizing low-end, low-use, low I/O applications such as test, development, log, file and print servers. "When it comes to edge-of-network, non-mission-critical applications that don't require high availability, you can stack dozens on a single machine," he says.

Bob Gill, managing director of server research at consultancy TheInfoPro, agrees. "Early on, people were virtualizing systems that had a less than 5% utilization rate. These were also the applications that, if they went down for an hour, no one got upset," he says.

That's not the case when applying virtualization to mission-critical, resource-intensive applications; virtualization vendors have been slow to explain this reality to customers, some say.

Once you get into applications with higher utilization rates, greater security risks and increased performance and availability demands, consolidation ratios drop off considerably. "These applications will compete for bandwidth, memory, CPU and storage," King says. Even on machines with two quad-core processors, highly transactional applications that have been virtualized will experience network bottlenecks and performance hits as they vie for the same server's pool of resources.

Start with a capacity analysis

To combat the problem, IT teams have to rework their thinking and dial back everyone's expectations. The best place to start: a capacity analysis, says Kris Jmaeff, information security systems specialist with Interior Health, one of five health authorities in British Columbia, Canada.

Four years ago, the data center at Interior Health was growing at a rapid rate. There was a lot of demand to virtualize the 500-server production environment to support a host of services, including DNS, ActiveDirectory, Web servers, FTP and many production application and database servers.

Before starting down that path, Jmaeff first used VMware tools to conduct an in-depth capacity analysis that monitored server hardware utilization. (Similar tools are also available from CiRBA, Hewlett-Packard, Microsoft, PlateSpin and Vizioncore, among others.) Rather than looking at his environment in a piecemeal fashion by each piece of hardware, he instead considered everything as a pool of resources. "Capacity planning should . . . focus on the resources that a server can contribute to the virtual pool," Jmaeff says.

Already, the team has been able to consolidate 250 servers, 50% of the server farm, onto 12 physical hosts. While Jmaeff's overall data center average is 20:1, hosts that hold more demanding applications either require much lower ratios or demand that he balance out resource-intensive applications.

Jmaeff uses a combination of VMware vCenter and IBM Director to monitor each VM for "telltale signs" of ratio imbalances such as spikes in RAM and CPU usage or performance degradation. "We've definitely had to bump applications around and adjust our conversion rates according to server resource demand to create a more balanced workload," he says. If necessary, it's easy to clone servers and quickly spread the application load, he adds.

"Because we did our homework with ratios of virtual servers by examining the load on CPU and memory and evaluated physical server workloads, we've been pleasantly surprised with our ratios," he says.

• Bookmark this page
• Share this article
  • facebook
  • slashdot
  • digg
  • Reddit
  • stumbleupon
  • linkedin
  • twitter
• Got more on this story? Email Computerworld
• Follow Computerworld on twitter

Comments