All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor@qumranet.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: performance tuning, problem with paravirtualized	clock
Date: Sun, 06 Apr 2008 23:49:01 +0300	[thread overview]
Message-ID: <1207514941.19397.45.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LRH.1.10.0804062044570.10628@linuxbox.linuxbox.cz>


On Sun, 2008-04-06 at 21:56 +0200, 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.
> - trying various block device backends (ide, scsi, virtio_blk) didn't 
> really matter much for my case
> - enabling CONFIG_KVM_GUEST under latest GIT with kvm-64 patch applied 
> decreased compile time by about 10%, which is nice!
> - enabling CONFIG_KVM_CLOCK made guest unstable, often unable to finish 
> booting at all, disabling acpi made it a bit better, but still quite 
> unstable (cpu0 lock-ups, etc)
> 
> 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?
> 

Can you try a non smp guest and check the results?
Also if you do try smp guest, can you pin each thread to a different
physical core and re-test?
Regards,
Dor

> anyways keep up the good work!
> cheers!
> nik
> 
> 
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel


-------------------------------------------------------------------------
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

  parent reply	other threads:[~2008-04-06 20:49 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 [this message]
2008-04-06 22:25   ` Nikola Ciprich
2008-04-07  4:14 ` Avi Kivity
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=1207514941.19397.45.camel@localhost.localdomain \
    --to=dor.laor@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.