From: Riccardo Brunetti <riccardo.brunetti@dnshosting.it>
To: kvm@vger.kernel.org
Subject: CPU Overcommitting question
Date: Fri, 18 Jul 2014 15:06:59 +0200 [thread overview]
Message-ID: <53C91BF3.6030507@dnshosting.it> (raw)
Dear KVM community people,
we are running on a kvm hypervisor with the following configuration:
CPU : Dual socket 6 cores: Intel(R) Xeon(R) CPU E5-2430 0 @ 2.20GHz
RAM : 48 GB
OS: CentOS release 6.5
2 very cpu intensive virtual machines and we are trying to find the best
way to optimize the available resources.
In particular what we would like to understand is how many vCPUs can be
assigned to each VM, in order to possibly exploit the overcommitting
features of the virtualization without degrading the performances.
The first question is about hyperthreading: should it be enabled and the
virtual cores be considered?
The second quesion is about the way to assign vCPUs between the two VMs.
Let's suppose we do not enable the hyperthreading, in our understanding
we have the following options:
1) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) = total number of physical
cores (12) (both VMs have < 12 vCPUs) (ie. 8+4)
2) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) > total number of physical
cores (12) (both VMs have <= 12 vCPUs) (ie. 12+8)
3) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) > total number of physical
cores (12) (one VM has > 12 vCPUs) (ie. 16+8)
4) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) > total number of physical
cores (12) (both VMs have > 12 vCPUs) (ie. 16+16)
According to your experience which would be the best one?
Thank you very much.
Kind Regards.
B. Riccardo
next reply other threads:[~2014-07-18 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 13:06 Riccardo Brunetti [this message]
2014-07-18 15:30 ` CPU Overcommitting question Paolo Bonzini
2014-07-18 16:49 ` riccardo.brunetti
2014-07-18 21:30 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53C91BF3.6030507@dnshosting.it \
--to=riccardo.brunetti@dnshosting.it \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox