From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Erik Jacobson <erikj@sgi.com>, kvm@vger.kernel.org
Subject: Re: slow guest performance with build load, looking for ideas
Date: Tue, 16 Jun 2009 11:07:54 +0300 [thread overview]
Message-ID: <4A3752DA.8060203@redhat.com> (raw)
In-Reply-To: <4A3743C1.6090108@msgid.tls.msk.ru>
On 06/16/2009 10:03 AM, Michael Tokarev wrote:
>>>>> So if I understand what you're saying: best not to use kvm guests
>>>>> for build
>>>>> servers with pre-Nehalem processors.
>>>>
>>>> pre-Nehalem / pre-Barcelona, > 4 vcpus, yes.
>>>
>>> How about 2 vcpus, and how about AMD processors ?
>>
>> 2 vcpus (or 4) should be fine. AMD processors (Barcelona+) would be
>> good for any number of vcpus.
> []
>
> Hmm.. that's sorta good (not so good for owners of most
> Intel CPUs -- Nehalem just started its life). But still
> confusing. Namely, 2..4 vcpus per GUEST or HOST -- for
> the ore-Nehalem ones? :)
4 vcpus per guest would be fine (even more should work, depending on
workload). Host will scale with any number of cpus.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-16 8:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 21:04 slow guest performance with build load, looking for ideas Erik Jacobson
2009-06-14 9:33 ` Avi Kivity
2009-06-15 14:15 ` Erik Jacobson
2009-06-15 14:24 ` Avi Kivity
2009-06-15 15:25 ` Michael Tokarev
2009-06-15 15:27 ` Avi Kivity
2009-06-16 7:03 ` Michael Tokarev
2009-06-16 8:07 ` Avi Kivity [this message]
2009-06-18 23:07 ` Erik Jacobson
2009-06-28 14:17 ` Avi Kivity
2009-06-28 19:05 ` Erik Jacobson
2009-06-28 21:28 ` Avi Kivity
2009-07-01 21:41 ` Erik Jacobson
2009-07-02 5:48 ` Avi Kivity
2009-07-02 9:41 ` Avi Kivity
2009-07-03 15:43 ` Mark McLoughlin
2009-07-03 16:28 ` Erik Jacobson
2009-07-09 2:36 ` Erik Jacobson
2009-07-09 7:48 ` Avi Kivity
2009-07-09 18:01 ` Erik Jacobson
2009-07-12 8:38 ` Avi Kivity
2009-07-16 12:20 ` Jes Sorensen
2009-07-25 14:33 ` Avi Kivity
2009-07-03 10:41 ` Matty
2009-07-05 8:07 ` Avi Kivity
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=4A3752DA.8060203@redhat.com \
--to=avi@redhat.com \
--cc=erikj@sgi.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.