Microsoft SQL Server runs at roughly 80% of native on VI3 in most benchmarked environments.  In production environments, and under loads that model those conditions, SQL Server runs at 90-95% of native on ESX 3.5.  I can say this with confidence despite a large amount of the industry's skepticism because I've spent so much time on SQL Server in the past half year.  I'd like to share some of my research on the subject and observations with you.

 

Two weeks ago my colleague Chethan Kumar and I presented on SQL Server in Cannes, France for VMworld Europe 2009.  This presentation was the culmination of six months of investigation that was started at VMworld 2008 in Las Vegas.  At that event I heard so many concerns about SQL Server performance that I was resolved to identify the problems.  I talked with every customer I could find that claimed that SQL ran at anything less than 70% of native.  So many of these contacts claimed that they had measured SQL at 25% of native or worse, that I knew that something was going wrong.

 

First, let me show you a slide that Chethan presented at the show in Cannes:

 

 

Chethan spent three months investigating SQL Server to find out how much he could improve virtual performance from the "out of the box" experience.  As this figure details, the sum total of performance improvements was 15%.  Here's another break-down of these results:

 

  

 

The only option that we found in ESX to improve virtual performance was static transmit coalescing, which is documented on page four of one of our SPECweb papers.  Large pages and SQL's priority boost, which are best practices provided by Microsoft for SQL Server configuration, provide the largest gains in performance.

 

The key messages that we communicated to our audience were that a properly running SQL Server should run at 80% of native or better.  In most production cases it can run at a performance indistinguishable from native speed.  And if performance is lagging, there don't exist many changes that can be made to ESX that can yield and performance gains at all.

 

This begs the question: "If ESX can't be tuned to double SQL performance, what is causing these reports of terrible SQL Server throughput?"  The great majority of the problems are coming from mis-configured storage.  But a variety of other items such as poor hardware selection or use of the wrong virtualization software contribute to the confusion, as well.  I've been documenting these issues in Best Practices for SQL Server on this community and will continue to update that document as more problems are discovered.

 

If you have a SQL Server running un-virtualized in your environment, I'd like you to try virtualizing it again.  Follow our best practices document and pay close attention to your storage configuration during deployment.  I feel confident that once you've setup your environment properly, you're going to like what you see.