Part 3 of a 5-part series based on my more than a decade of virtualization experience with large enterprises and service providers, and my time running strategic planning for one of the largest 2 virtualization vendors, this blog series covers 10 types of situations when you should consider not virtualizing some of your applications.
Reason 5: When you work for a cheapskate
Sorry, like an worthwhile IT project, virtualization requires a budget. If you don’t have a way to pay for the project, don’t start it. Halfway implemented virtualization without adequate tools is worse than whatever you have today.
Reason 6: When you’re already running servers at high capacity
Adding a hypervisor to a pegged server does nothing to help performance. While we’ve made major progress in the last decade to reduce the CPU overhead taken by a hypervisor, it’s still an additional load on the CPU. In this case, buying another server just to provide cycles for a hypervisor isn’t a good investment. This is why few very high scale sites like Facebook and Google virtualize most of their operational servers.
Next up: Reasons 7 and 8 in the series about why not to virtualize.