Home > Blogs > VMware VROOM! Blog

Performance Best Practices for VMware vSphere 5.0

A new version of Performance Best Practices for vSphere is now available.  This is a book designed to help system administrators obtain the best performance from vSphere deployments.

We've addressed many of the new features in vSphere 5.0 from a performance perspective.  These include:

  • Storage Distributed Resource Scheduler (Storage DRS), which performs automatic storage I/O load balancing
  • Virtual NUMA, allowing guests to make efficient use of hardware NUMA architecture
  • Memory compression, which can reduce the need for host-level swapping
  • Swap to host cache, which can dramatically reduce the impact of host-level swapping
  • SplitRx mode, which improves network performance for certain workloads
  • VMX swap, which reduces per-VM memory reservation
  • Multiple vMotion vmknics, allowing for more and faster vMotion operations

We've also significantly updated and expanded many of the topics we've covered in previous editions of the book.  These include:

  • Choosing hardware for a vSphere deployment
  • Power management
  • Configuring ESXi for best performance
  • Guest operating system performance
  • vCenter and vCenter database performance
  • vMotion and Storage vMotion performance
  • Distributed Resource Scheduler (DRS) and Distributed Power Management (DPM) performance
  • High Availability (HA), Fault Tolerance (FT), and VMware vCenter Update Manager performance

The book can be found at: Performance Best Practices for VMware vSphere 5.0.


4 thoughts on “Performance Best Practices for VMware vSphere 5.0

  1. Chris Nakagaki

    With previous versions of vSphere, it was recommended that the C and C1E states be disabled. With ESX 4.1 on Dell servers, having these BIOs settings enabled would cause PSOD’s randomly. Has something in ESXi 5.0 changed to prevent this somewhat rare issue? http://tech.zsoldier.com/2011/08/esxesxi-recommended-bios-settings.html

  2. Qasim Ali

    Hi Chris,
    We at VMware are not aware of any issue where C-states or C1E causes PSODs. The reason we suggested that users consider disabling C1E in the BIOS for previous releases was not to provide better stability. It was only to improve performance with certain latency-sensitive workloads.
    There is a new white paper on Host Power Management for vSphere 5.0 that includes information about C-states and C1E:

  3. Chris Nakagaki

    Thanks for the clarification. Appreciate it.

  4. Pingback: VMware vSphere Best Practices | Virtualbits

Leave a Reply

Your email address will not be published. Required fields are marked *