Fixed recommendations for consolidation ratios are cancerous. Whether we are talking about vCPUs per core, virtual machines per host, or VMDKs per LUN, there is no single number the represents the “right” ratio. Accurate guidance requires workload characterization and fine tuning using vSphere’s performance counters. Today I want to highlight one experiment that shows application choice impacting VMDK-to-LUN consolidation. The inescapable conclusion is that sequential access data must be separated from random access files!
Virtual Storage Design: Application Consolidation
Top Five VROOM! Entries for 2009
I love VMware’s performance blog, VROOM! It is our most popular performance communication vehicle and its content is backed by a stellar engineering team with unmatched integrity. Each article details the nuances of VMware performance and educates on application and platform best practices. I love all the articles but am always surprised as to which our readers find most popular. Here is a countdown of the five entries most read in 2009.
ESX Memory Management: Ballooning Rules
[Taken from my communities blog, this article shows you why you should "Love Your Balloon Driver".]
Earlier this month we finally published one of my favorite papers from ongoing vSphere launch activities. This paper on ESX memory management, written by Fei Guo of performance engineering, has three graphs that are absolute gems. They show balloon driver memory savings next to throughput numbers for three common benchmarks. The conclusion is inescapable: the balloon driver reclaims memory from over-provisioned VMs with virtually no impact to performance. This is true on every workload save one: Java.
Read the rest of this entry »