From: Paolo Bonzini <bonzini@gnu.org>
To: riccardo.brunetti@dnshosting.it, Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <paolo.bonzini@gmail.com>
Subject: Re: CPU Overcommitting question
Date: Fri, 18 Jul 2014 23:30:15 +0200 [thread overview]
Message-ID: <53C991E7.1000909@gnu.org> (raw)
In-Reply-To: <705c3521045351691bbb7e00f52de710@dnshosting.it>
Il 18/07/2014 18:49, riccardo.brunetti@dnshosting.it ha scritto:
> So, it should be ok to have the first two options, but also considering
> that with hyperthreading instead of 12 cores we can consider 24? Thus we
> can go with:
>
> 1) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) = total number of cores
> (24) (both VMs have < 24 vCPUs) (ie. 18+6)
> 2) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) > total number of cores
> (24) (both VMs have <= 24 vCPUs) (ie. 24+10)
Yes.
Something between 12 and 24 will probably give the best performance.
Paolo
prev parent reply other threads:[~2014-07-18 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 13:06 CPU Overcommitting question Riccardo Brunetti
2014-07-18 15:30 ` Paolo Bonzini
2014-07-18 16:49 ` riccardo.brunetti
2014-07-18 21:30 ` Paolo Bonzini [this message]
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=53C991E7.1000909@gnu.org \
--to=bonzini@gnu.org \
--cc=kvm@vger.kernel.org \
--cc=paolo.bonzini@gmail.com \
--cc=pbonzini@redhat.com \
--cc=riccardo.brunetti@dnshosting.it \
/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