From: Steve Ofsthun <sofsthun@virtualiron.com>
To: deshantm@gmail.com
Cc: Daniel Magenheimer <dan.magenheimer@oracle.com>,
xen-devel mailing list <xen-devel@lists.xensource.com>
Subject: Re: Poor performance on HVM (kernbench)
Date: Wed, 10 Sep 2008 17:51:55 -0400 [thread overview]
Message-ID: <48C8417B.7050101@virtualiron.com> (raw)
In-Reply-To: <1e16a9ed0809101442q225c5fcfj25c0b4ffe0da83a0@mail.gmail.com>
Todd Deshane wrote:
> On Wed, Sep 10, 2008 at 5:37 PM, Daniel Magenheimer
> <dan.magenheimer@oracle.com> wrote:
>> This doesn't answer the HVM question but it appears that
>> you are running guests with 1 vCPU but comparing against
>> a dual-CPU native. True?
>
> Yes. The intuition is that we don't want to overcommit virtual CPUs
> since then you are stressing the schedulers more.
I think what Dan is getting at is, the native execution run should restrict it's cpu and memory usage to be identical with the guest tests. So restrict the native test cpus with "maxcpus=1" or "nosmp" on the boot line. Similarly you can restrict memory using "mem=xxxM".
> I ran some tests with 2 vCPUs and all the numbers are a bit higher (as
> having two CPUs tackling a compile is faster).
>
> Although overcommit (of CPUs and memory ;) is interesting, we leave a
> CPU dedicated to the host system (linux/dom0)
> on purpose.
>
> Todd
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-09-10 21:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 18:23 Poor performance on HVM (kernbench) Todd Deshane
2008-09-10 21:22 ` Todd Deshane
2008-09-10 22:42 ` Anthony Liguori
2008-09-11 2:52 ` Todd Deshane
2008-09-11 9:35 ` George Dunlap
2008-09-11 15:30 ` Todd Deshane
2008-09-11 10:00 ` Gianluca Guida
2008-09-11 15:17 ` Gianluca Guida
2008-09-11 15:25 ` Gianluca Guida
2008-09-11 15:35 ` Todd Deshane
2008-09-11 16:48 ` Gianluca Guida
2008-09-11 17:25 ` Gianluca Guida
2008-09-11 18:07 ` George Dunlap
2008-09-11 18:26 ` Gianluca Guida
2008-09-11 19:04 ` Todd Deshane
2008-09-11 19:54 ` Todd Deshane
2008-09-11 20:02 ` Jeremy Fitzhardinge
2008-09-11 20:24 ` John Levon
2008-09-12 10:41 ` Gianluca Guida
2008-09-12 11:04 ` George Dunlap
2008-09-12 11:19 ` George Dunlap
2008-09-12 14:20 ` Jeremy Fitzhardinge
2008-09-10 21:37 ` Daniel Magenheimer
2008-09-10 21:42 ` Todd Deshane
2008-09-10 21:45 ` Daniel Magenheimer
2008-09-11 2:48 ` Todd Deshane
2008-09-10 21:51 ` Steve Ofsthun [this message]
2008-09-11 2:50 ` Todd Deshane
2008-09-11 6:31 ` Pasi Kärkkäinen
2008-09-11 16:02 ` Todd Deshane
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=48C8417B.7050101@virtualiron.com \
--to=sofsthun@virtualiron.com \
--cc=dan.magenheimer@oracle.com \
--cc=deshantm@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.