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

[Xen-devel] httperf throughput

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] httperf throughput
From: "Apparao, Padmashree K" <padmashree.k.apparao@xxxxxxxxx>
Date: Thu, 14 Sep 2006 21:49:44 -0700
Delivery-date: Thu, 14 Sep 2006 21:50:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbYgl0igLSANY1GSjmNAwRs43yLfg==
Thread-topic: httperf throughput

Hi,

 

I am running apache and httperf on the latest Xen unstable.

 

When I have the webserver running in a single cpu guest I can barely get 720 Mbps over 2 nics (each 1 Gb). That is the throughput is about 36% of the native linux throughput. (I get line rate on native linux with the cpu being fully utilized). The guest cpu is 100% utilized while dom0 is about 80% utilized.

 

Said another way, I can get 2000 connections per second in Xen before the cpu chokes while in Linux I get about 7000 connections per sec. Is this what is expected.

 

Does anyone have similar/alternate performance data to share?

Thanks

-          Padma

-            

 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>