From: Alec Istomin <alec@openvz.org>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: vCPU scalability for linux VMs
Date: Wed, 5 May 2010 09:56:02 -0700 [thread overview]
Message-ID: <1741493606.20100505095602@istomin.de> (raw)
In-Reply-To: <4BE12FB4.1090303@redhat.com>
On Wednesday, May 5, 2010 at 04:43:32 -0400, Avi Kivity wrote:
> So you have a total of 32 vcpus on 8 cores? This is known to be
> problematic. You may see some improvement by enabling hyperthreading.
exactly, 32 vCPUs on 8 core hardware that doesn't support hyperthreading
(Clovertown E5335)
> There is ongoing work to improve this.
If interested - let me know when is it going to be a good time/build to
do the regression on this.
next prev parent reply other threads:[~2010-05-05 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 1:45 vCPU scalability for linux VMs Alec Istomin
2010-05-05 8:43 ` Avi Kivity
2010-05-05 16:56 ` Alec Istomin [this message]
[not found] ` <AANLkTinDKDV3vwLiZzmMC6C4cjOnXT1H-joJ4rcR3vgA@mail.gmail.com>
2010-05-05 17:27 ` Fwd: " Srivatsa Vaddagiri
2010-05-05 19:31 ` Alec Istomin
2010-05-06 5:53 ` Srivatsa Vaddagiri
2010-05-06 7:58 ` Alec Istomin
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=1741493606.20100505095602@istomin.de \
--to=alec@openvz.org \
--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