vsphere_static_160x300
Badges

vexpert_logo_100x57

gestaltitbadge

follow-me-twitter

Subscribe to me on FriendFeed

Comments / DISQUS
Feedjit.com

My Rant about “The Benchmark”

Hypervisor Test Explained is a Virtualization Review post by Rick Vanover written in response to the fallout over “The Benchmark”. Real quick for those few that do not know, Rick, along with Editor in Chief Keith Ward, recently published (in Rick’s words) “a comparative performance test” for VMware ESX, Microsoft Hyper-V, and Citrix XenServer. The results of that test have been hotly debated since. Mostly between VMware and Citrix, but other skirmishes in the form of comments, tweets, and blog posts have also popped up scattered around the virtualization blogisphere. Until recently I’ve sat on the fence about the test results and the reactions. Partly because I found the test’s outcome startling, but also because I found myself disagreeing with the position and opinions of both sides as I watched the battle.

Now, before I continue let me establish that I immediately questioned why this was even being debated as a hypervisor “benchmark” at all. In my mind it was always what Rick describes now: a comparitive test. The goal wasn’t to say hypervisor A, B, and C can do X amount of Y and Z. Rick’s comment on Jason Boche’s early post on this topic makes it crystal clear what his objective really was:

“… everyone is assuming I’m offering this as information for the enterprise. Not so. I really am targeting this to the customer who is going to select the free hypervisors for small, unmanaged installations.”

To satisfy me for “small unmanaged installations”


all you have to do is use the same hardware, the same VMs, the same applications, and the same test processes. That’s a fair test for a defined scenario. It’s real world. The hypervisors are installed out of the box by SMB administrators. The configurations are left at the defaults. Rick describes it best:

“We have CPU hogs and memory beasts that we want to get virtual, and the canned response of an application not being a virtualization candidate is a warning we may not heed by choice. We work with default configurations because we don’t always have the time or other resources to go about it another way. We don’t work with “camera-ready” databases.

On the other hand, don’t claim absolute victory either. You can proclaim yourself today’s winner in the “small unmanaged installations” scenario. I’ll help you do it, but you cross the line with me when you make broad and general statements based on this test. Wait until 6 months from now when Rick and Keith do the same test (hopefully) with shared storage or all 64 bit hypervisors for example?

In closing, Keith Ward brought up a point I feel needs to be re emphasized in one of his responses to the fallout:

“And I don’t know how I can state it any more clearly: This test only determined one aspect of these hypervisors. To make a buying decision based on this article would be foolish in the extreme.”

Now, if we are going to really benchmark hypervisors then Chris Wolf’s cry for SPECvirt independent testing is the way to go. Let’s hope we get there. I also applaud Chris for organizing a public debate on this topic as well give a standing ovation to both VMware and Citrix for agreeing to participate in The Thrilla in California. I only wish I could be there on July 29 in San Diego to cover this in person!

Related Posts

  • Good post, Rich. Too bad you can't make it out to Catalyst. I get the feeling that a video of The Thrilla is going to make it's way to YouTube, so hopefully you'll still get a chance to see the debate online. It should be a good (and hopefully productive) debate.
  • Chris,

    Thanks! I'll definitely look for the video online and watch your blog for the inside scoop too!
  • and with You I meant the guys that did the review of course :-D
  • Duncan,

    Thanks for the comments. I agree, no real winner or loser and it's not right to call it a real benchmark.
  • I think that this test didn't determined anything at all. If you look at the number of differences between amount of operations handled there's no way you can call this a performance benchmark or a comparison, or even declare a winner or looser. The only thing that's a fact is that they didn't use a controlled environment and the outcome of the tests heavily fluctuated on the moment and the background processes that were running.

    There comment that they work with all the default because they don't have enough time to do otherwise clearly shows that they shouldn't be doing comparisons on this level. Or they should have randomized it in such a high amount that the external influences didn't matter anymore, but they probably also didn't have time to do that.

    I'm not trying to defend VMware because I'm an employee, but I think you need to stick with what your good at. My view on this topic along other performance issues: http://www.yellow-bricks.com/2009/03/14/perform...
blog comments powered by Disqus
Hyper9 Cowabunga
Support VM /ETC
Support VMETC.com

Support VMETC.com

Free Business and Tech Magazines and eBooks
@rbrambley tweets
Advertisements
VMTN Roundtable Podcasts
Subscribe



Add to Google Reader or Homepage
Subscribe in NewsGator Online
Add to netvibes
Add to Plusmo