All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Avi Kivity <avi@redhat.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
	Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, anthony@codemonkey.ws, avi@qumranet.com
Subject: Re: First performance numbers
Date: Sat, 20 Sep 2008 08:55:05 +0200	[thread overview]
Message-ID: <20080920065505.GJ27426@8bytes.org> (raw)
In-Reply-To: <48D4524A.80902@redhat.com>

On Fri, Sep 19, 2008 at 06:30:50PM -0700, Avi Kivity wrote:
> Joerg Roedel wrote:
> >Ok, here are some performance numbers for nested svm. I ran kernbench -M
> >on a virtual machine with 4G RAM and 1 VCPU (since nesting SMP guests
> >do currently not work). I measured simple virtualization with a shadow
> >paging guest on bare metal and within a nested guest (same guest image)
> >on a nested paging enabled first level guest.
> >
> >                 | Shadow Guest (100%) | Nested Guest (X)  | X
> >-----------------+---------------------+-------------------+--------
> >Elapsed Time     | 553.244 (1.21208)   | 1185.95 (20.0365) | 214.363%
> >User Time        | 407.728 (0.987279)  | 520.434 (8.55643) | 127.642% 
> >System Time      | 144.828 (0.480645)  | 664.528 (11.6648) | 458.839%
> >Percent CPU      | 99 (0)              | 99 (0)            | 100.000%
> >Context Switches | 98265.2 (183.001)   | 220015 (3302.74)  | 223.899%
> >Sleeps           | 49397.8 (31.0274)   | 49460.2 (364.84)  | 100.126%
> >
> >So we have an overall slowdown in the first nesting level of more than
> >50%. Mostly because we spend so much time in the system level. Seems
> >there is some work to do for performance improvements :-)
> >
> >  
> 
> Do you have kvm_stat output for the two cases?  Also interesting to run 
> kvm_stat on both guest and host.

Sorry, no. But I can repeat the measurements and gather these numbers.

Joerg


      reply	other threads:[~2008-09-20  6:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 13:41 [PATCH 0/9] Add support for nested SVM (kernel) v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 1/9] Add CPUID feature flag for SVM v3 Alexander Graf
2008-09-17 13:41   ` [PATCH 2/9] Clean up VINTR setting v3 Alexander Graf
2008-09-17 13:41     ` [PATCH 3/9] Add helper functions for nested SVM v3 Alexander Graf
2008-09-17 13:41       ` [PATCH 4/9] Implement GIF, clgi and stgi v3 Alexander Graf
2008-09-17 13:41         ` [PATCH 5/9] Implement hsave v3 Alexander Graf
2008-09-17 13:41           ` [PATCH 6/9] Add VMLOAD and VMSAVE handlers v3 Alexander Graf
2008-09-17 13:41             ` [PATCH 7/9] Add VMRUN handler v3 Alexander Graf
2008-09-17 13:41               ` [PATCH 8/9] Add VMEXIT handler and intercepts v3 Alexander Graf
2008-09-17 13:41                 ` [PATCH 9/9] Allow setting the SVME bit v3 Alexander Graf
2008-09-19 15:59               ` [PATCH 7/9] Add VMRUN handler v3 Joerg Roedel
2008-09-25 17:32                 ` Alexander Graf
2008-09-25 17:37                   ` Joerg Roedel
2008-09-25 20:00                     ` Alexander Graf
2008-09-25 21:22                       ` joro
2008-09-27 12:59                         ` Avi Kivity
2008-09-27 12:58                       ` Avi Kivity
2008-09-25 18:47         ` [PATCH 4/9] Implement GIF, clgi and stgi v3 Joerg Roedel
2008-09-25 19:55           ` Alexander Graf
2008-09-25 21:27             ` Joerg Roedel
2008-09-26  9:01               ` Alexander Graf
2008-09-27 12:55                 ` Avi Kivity
2008-09-27 12:52           ` Avi Kivity
2008-09-19 14:36 ` [PATCH 0/9] Add support for nested SVM (kernel) v3 Joerg Roedel
2008-09-19 14:39   ` Joerg Roedel
2008-09-19 15:56   ` Joerg Roedel
2008-10-15 17:07     ` Alexander Graf
2008-09-19 21:48 ` First performance numbers Joerg Roedel
2008-09-20  1:30   ` Avi Kivity
2008-09-20  6:55     ` Joerg Roedel [this message]

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=20080920065505.GJ27426@8bytes.org \
    --to=joro@8bytes.org \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=avi@redhat.com \
    --cc=joerg.roedel@amd.com \
    --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 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.