Resource Allocation Rule of Thumb

Home Forums Virtualization VMware Virtualization Resource Allocation Rule of Thumb

This topic contains 2 replies, has 3 voices, and was last updated by  Nonapeptide 8 years, 10 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts

  • Flaxter
    Member
    #146543

    I was wondering about a general rule of thumb for resource allocation.

    What I mean by this, is if you have a host with ‘X’ cores & ‘Y’ RAM, how many VM’s worth of ‘A’ cores & ‘B’ RAM would you deploy?

    A lot of people over allocate resources, and am just wondering what the general rule of thumb for this would be.


    Nonapeptide
    Member
    #317139

    Re: Resource Allocation Rule of Thumb

    Seems like this is a bit of a “How long is a piece of string” question. If the VMs are just idling, I’d say you could over commit them indefinitely. I’ve never heard of a general rule or ratio for over committing resources.


    simondrake79
    Member
    #237696

    Re: Resource Allocation Rule of Thumb

    The thing to remember is resource allocation is dynamic; you can change it as when necessary

    Start off with 1 vCPU for EVERY virtual machine you create (unless OS or software require more). This article explains some of the reasons why you should use 1 vCPU and not load the VM up:

    http://209.85.229.132/search?q=cache:http%3A%2F%2Flonesysadmin.net%2F2008%2F04%2F22%2Fwhy-my-two-vcpu-vm-is-slow%2F

    It’s ok to over allocate on memory as mentioned before. When the VM is up and running check on the Resource Allocation tab of the VM. This can tell you if you need to make amendments to allocations. Keep an eye on the Ballooned figure; if you start to see large amounts of ballooning then this can be down to paging faults. Also keep an eye on the Swapped figure.

    Be careful using shares, only use these if you are experiencing resource constraints.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.