WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Poor performance on HVM (kernbench)

To: "Steve Ofsthun" <sofsthun@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Poor performance on HVM (kernbench)
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Wed, 10 Sep 2008 22:50:29 -0400
Cc: Daniel Magenheimer <dan.magenheimer@xxxxxxxxxx>, xen-devel mailing list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 10 Sep 2008 19:50:53 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=rDIu73sCRJMZnaf0N6Z53gX29c3AYEbOdjmzX5DmD+A=; b=SQNAmk6btzOxBITUyMj75skhrWh8KGrKRJ36DPePMNRDAutK1pygoaF5jGJeQTpm4+ NNtV/Xzb7daLvsNWaq9jsxXUR0gYZZ23PhvBV0Lm1gdhe9UWZVkerTYKoDbFIcN2SXot xIM9qKQuZ/44/Dh8Ud6FmquBXWUmzw57vM0Vs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=vqrPo5LBV4XCxvbMWwPKMh/Nsxp/bTbyhcTkYA1HR5xvUIQQ7UjR23W4MQz9OqaMhd 2IKPO6N83gzSqn3ptM2AV1srsLwZybqjHg1f1oMcu3fsQBCcAHNjVBs/i65w1oEayLiU VXystNkGX5hC7AkK5Njj2HQjL+bFDxCrHTxsk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48C8417B.7050101@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1e16a9ed0809101123m71a12030v7d06501f6467f93@xxxxxxxxxxxxxx> <e0f1c7f4-7bc5-4d64-8409-464ade1d749f@default> <1e16a9ed0809101442q225c5fcfj25c0b4ffe0da83a0@xxxxxxxxxxxxxx> <48C8417B.7050101@xxxxxxxxxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> 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".

Linux kernel (only had a spare Ubuntu 2.6.24) to work with

nosmp  mem=2048M

Average Optimal load -j 4 Run (std deviation):
Elapsed Time 403.744 (0.26857)
User Time 373.23 (0.421485)
System Time 30.32 (0.389551)
Percent CPU 99 (0)
Context Switches 90961.2 (105.838)
Sleeps 52311.8 (83.8373)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel