Virtualisation - Over Committing resources


Do you Over commit resources  

12 members have voted

  1. 1. Do you Over Commit on CPU

    • Yes
      4
    • No
      5
    • Depends on the VMs function
      2
  2. 2. Do you Over Commit on RAM

    • Yes
      3
    • No
      8
    • Depends on the VMs function
      0
  3. 3. Do you Over Commit on VHD

    • Yes
      4
    • No
      4
    • Depends on the VMs function
      3


Recommended Posts

As the title suggests, I'm curious what peoples thoughts are (in an Enterprise environment) when it comes to over committing on resources, I'm sure there are a lot of variables that you all consider when putting systems in place but I'm just looking for an in general point of view.

 

The company I work for is mainly Hyper-V but we do have a few ESX hosts too, but in general we always over commit on CPU and HDD (Dynamically expanding disks) however on the whole Memory is always statically set on Hyper-V bar one or two clusters whereas in Vmware its generally left with no restrictions.

Link to comment
Share on other sites

Always on CPU and Disk.  Never on RAM because modern OSs run better by using all of the memory available to them.  You don't want to be swapping, because it makes the VM slow.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.