From: Avi Kivity <avi@qumranet.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: performance tuning, problem with paravirtualized clock
Date: Mon, 07 Apr 2008 07:14:39 +0300 [thread overview]
Message-ID: <47F99FAF.1050205@qumranet.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0804062044570.10628@linuxbox.linuxbox.cz>
Nikola Ciprich wrote:
> Hi,
> I spent some time trying to tune performance of KVM guest using kernel
> compilation as a kind of benchmark (I'm using virtual machines for
> compiling a lot, so it's good benchmark for me in general)
>
> Host machine: 2x quad core XEON E5420 @ 2.50GHz, 4GB RAM, 2.6.24 + kvm-64
> guest configuration: all 8 cores available, 2GB RAM, 2.6.24 or latest GIT
> + kvm-64
>
> some results:
> - compilation in KVM guest is roughly 2x slower than on bare metal.
>
50% scaling is actually quite good for 8-way.
What do you get for 4-way guests?
> - enabling CONFIG_KVM_GUEST under latest GIT with kvm-64 patch applied
> decreased compile time by about 10%, which is nice!
>
>
We expect to improve this some more as paravirt_ops improves.
> Is there currently anything more I could do to improve performance? I'm
> wandering what is slowing compilation, if I compare some CPU intensive
> application (ie bzip2), it seems to run in nearly native speed, but kernel
> compilation is much slower even if run from ramdisk, maybe it could be
> improved further by tunning scheduler etc?
>
>
As others mentioned, large pages may help somewhat, as well as newer
hardware. kvm-65 also improves scalability.
How much cpu does the qemu process consume? Perfect utilization would
be around 800%. What's the system/user ratio (I think you need to use
2.6.25-rc to get accurate results for this)?
Can you provide the result of 'kvm_stat -1' taken a few times during a
compile run?
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-07 4:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 19:56 performance tuning, problem with paravirtualized clock Nikola Ciprich
2008-04-06 20:38 ` Anthony Liguori
2008-04-06 21:57 ` Nikola Ciprich
2008-04-06 22:08 ` Anthony Liguori
2008-04-06 22:24 ` Nikola Ciprich
2008-04-06 22:33 ` Anthony Liguori
2008-04-06 20:49 ` Dor Laor
2008-04-06 22:25 ` Nikola Ciprich
2008-04-07 4:14 ` Avi Kivity [this message]
2008-04-07 15:41 ` Marcelo Tosatti
2008-04-07 20:47 ` Nikola Ciprich
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=47F99FAF.1050205@qumranet.com \
--to=avi@qumranet.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm-devel@lists.sourceforge.net \
/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.