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-users

Re: [Xen-users] Xen Performance

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] Xen Performance
From: Grant McWilliams <grantmasterflash@xxxxxxxxx>
Date: Wed, 14 Oct 2009 00:06:54 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Oct 2009 00:07:59 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=rMiXg+S6mR5wZUYZ4qYw1v/a0PmsrqVQrutmyIGRX/c=; b=vBmSCa/7Mx5M0nz7G8JLswr9pLaP2smgt1kdVugem4Qrqi/SSAmYMSfgUfuXapK2pZ 6EMDpfYr2nCDTddS6IFN4rxqlShrPqaYZsDBl0nV8lOJ/TLlnmsN6oDZhjE9bSy1Y0vq VS7D/OTsNf0pPz2bZjejFrebzTvOju2Cyqo5o=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=DMNJO2Ix5hqT2OExBROL6mkmh1eRaRu84rT0gzg5yx2watnmJBPFvU9edNWVnseN6W eNrY1F3njKwTXjy2O7dayUje6knx9tfXrUmFyk26WH6RLsOKi+dmloxelor+P1V0yjZ3 KDGFYo72Fq1pwlr6YQgGnNTB4Wu/u3oGBZj3A=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0910132318m1561766cvdff28966154161f@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <713143895.20091010125310@xxxxxxxxxxxxx> <7207d96f0910121900r183dfe7bv75ee3fbeb33aa716@xxxxxxxxxxxxxx> <ed123fa30910121917v48d3fef3rd06ef86d090efc15@xxxxxxxxxxxxxx> <7207d96f0910130008t5e6d81b7x89afb027d1489999@xxxxxxxxxxxxxx> <ed123fa30910130105v28545580g48a3bad26c774d5c@xxxxxxxxxxxxxx> <7207d96f0910130506l4887cdcdp9858c01685635d80@xxxxxxxxxxxxxx> <ed123fa30910131054w53661924ga62bea6262d87392@xxxxxxxxxxxxxx> <7207d96f0910132318m1561766cvdff28966154161f@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On Tue, Oct 13, 2009 at 11:18 PM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
On Wed, Oct 14, 2009 at 12:54 AM, Grant McWilliams
<grantmasterflash@xxxxxxxxx> wrote:
> CentOS 5.4? If my time machine worked :-) . I'm already running CentOS 5.3
> with Gitco's Xen 3.4.1.
>
> Here's another system: CentOS 5.3 Dom0, CentOS 5.3 DomUs on a Dual Core Duo
> Xeon system (2.8ghz)
>
> DomU to DomU -  1.93 Gbits/sec
> DomU to Dom0 -  2.76 Gbit/sec
> Dom0 to DomU -  193 Mbits/sec

Ah ... so domU <-> domU is working FINE, right? That is similar with
the results I get :

It isn't working fine. I said at the end of my message that the numbers aren't quite right because I didn't post both halves of the bidirectional test. The second half is 1/4 the speed of the first.

Can you post the whole bidirectional test for DomU to DomU like the one below? As soon as I get my Virtual Server back up I'll post full numbers. I didn't realize until the end of the test that I was only recording one direction. The reverse direction numbers are 1/4 the speed. Anyway I'll do more comprehensive testing.

 
As for dom0 -> domU performance, it is indeed lower, and I'm not sure
why. In my case it's still usable though (about 600-800 Mbps), since I
don't run any service on dom0 that is used by domU. Here's my dom0 <->
domU result.

# iperf -c 192.168.122.1 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.122.1, TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  5] local 192.168.122.49 port 52890 connected with 192.168.122.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec  2.72 GBytes  2.34 Gbits/sec
[  4] local 192.168.122.49 port 5001 connected with 192.168.122.1 port 16809
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec    747 MBytes    627 Mbits/sec
 

192.168.122.1 -> dom0's virbr0, running RHEL5.4 64bit,
kernel-xen-2.6.18-164.2.1.el5, Xen 3.4.1.
192.168.122.49 -> domU, kernel-xen-2.6.18-164.2.1.el5

I'm not sure why your dom0 -> domU is about 3 times slower than mine.
Perhaps newer kernel version matters.

--
Fajar

 

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