From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Ofsthun Subject: Re: Poor performance on HVM (kernbench) Date: Wed, 10 Sep 2008 17:51:55 -0400 Message-ID: <48C8417B.7050101@virtualiron.com> References: <1e16a9ed0809101123m71a12030v7d06501f6467f93@mail.gmail.com> <1e16a9ed0809101442q225c5fcfj25c0b4ffe0da83a0@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1e16a9ed0809101442q225c5fcfj25c0b4ffe0da83a0@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: deshantm@gmail.com Cc: Daniel Magenheimer , xen-devel mailing list List-Id: xen-devel@lists.xenproject.org Todd Deshane wrote: > On Wed, Sep 10, 2008 at 5:37 PM, Daniel Magenheimer > 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