public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Poor KVM guest performance on an HP rack server
Date: Sun, 13 Dec 2009 10:29:52 -0800	[thread overview]
Message-ID: <4B2532A0.2070001@goop.org> (raw)
In-Reply-To: <4B24BE17.805@pardus.org.tr>

On 12/13/09 02:12, Ozan Çağlayan wrote:
> Hmm, that's because we're using/developing a Linux distribution which
> doesn't have 64-bit support yet. But since the guest will be a
> compile-farm for our needs, it's worth trying to run an 64-bit distro on
> the host to see the difference, thanks for the tip but how much should
> this affect the performance?

32-bit PAE is marginal above 4G of memory and the limit is at about 8G.  
Above that, so much lowmem (<~1GB) is occupied by page and other kernel 
structures that there's barely any memory to do any real work.  If this 
is what's happening, you'd expect to see poor host performance, and slow 
guest performance would be secondary to that.

With 64-bit, all the memory can be directly addressed so none of this 
applies.  I would expect to see significant performance gains.

There's nothing to stop you from running 32-bit PAE guests, so you can 
do your distro development that way (at least in part).

     J

  reply	other threads:[~2009-12-13 18:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13  0:54 Poor KVM guest performance on an HP rack server Ozan Çağlayan
2009-12-13  6:10 ` Jeremy Fitzhardinge
2009-12-13 10:12   ` Ozan Çağlayan
2009-12-13 18:29     ` Jeremy Fitzhardinge [this message]
2010-03-12 17:18       ` Ozan Çağlayan
2010-03-13  8:21         ` Avi Kivity
2009-12-13 10:13 ` Avi Kivity
2009-12-13 11:36   ` Ozan Çağlayan
2009-12-13 11:58     ` Ozan Çağlayan
2009-12-15 10:29       ` 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=4B2532A0.2070001@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ozan@pardus.org.tr \
    /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