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 03:15:00 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Oct 2009 03:16:07 -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=wqcUYmpAc3A/Dl6BuhMMlkdMy/Pn5CXBv7toCWfDEyQ=; b=BO6c6ZIX4CrvDe5RwhmNDTzw7hZVR9k56Djab3Wdz0ukgka/QE1k8jQ5Nd/EHRV4zC V9HXg0P9EX5Qbsa6GbMweIQPCrIjuTfoLOBwRkwmxdRec0zFFIrKI/EgYgpomVxnG8q0 7FwXp1IWLaWW3J7E830812Ypg+VAIBK1tnM7w=
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=EO7FyQAh0Q3Zf76fUyzfpStYs0AVmnDyygfsOsoqUHkZg9u/+Zr7zPm0iP5KPun22s A+dBxc7/QjBrj/82vDeRsyhFqxg/whAB+rK//W77PyC80Yn5mbaUCWTfyoHvtYn6NH7K 4G4oTF1phWUd1a7K6ADO2c9Ock1WpqpbFW9wU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <ed123fa30910140302v5dd0f963mac003cb27852af39@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> <ed123fa30910121917v48d3fef3rd06ef86d090efc15@xxxxxxxxxxxxxx> <7207d96f0910130008t5e6d81b7x89afb027d1489999@xxxxxxxxxxxxxx> <ed123fa30910130105v28545580g48a3bad26c774d5c@xxxxxxxxxxxxxx> <7207d96f0910130506l4887cdcdp9858c01685635d80@xxxxxxxxxxxxxx> <ed123fa30910131054w53661924ga62bea6262d87392@xxxxxxxxxxxxxx> <7207d96f0910132318m1561766cvdff28966154161f@xxxxxxxxxxxxxx> <ed123fa30910140006w60ffadd3mc646162c1f77bde3@xxxxxxxxxxxxxx> <7207d96f0910140219k3de594f7mfcd7dbea9aff7c58@xxxxxxxxxxxxxx> <ed123fa30910140302v5dd0f963mac003cb27852af39@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Grant McWilliams

Some people, when confronted with a problem, think "I know, I'll use Windows."
Now they have two problems.



On Wed, Oct 14, 2009 at 3:02 AM, Grant McWilliams <grantmasterflash@xxxxxxxxx> wrote:
On Wed, Oct 14, 2009 at 2:19 AM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
On Wed, Oct 14, 2009 at 2:06 PM, Grant McWilliams
<grantmasterflash@xxxxxxxxx> wrote:
> 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:

>> > DomU to DomU -  1.93 Gbits/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.

I posted the result for self-compiled 2.6.29-xen domU in my second
mail on this thread (I got around 1-2 Gbps). Here's one for domU with
RHEL's kernel-xen-2.6.18-164.2.1.el5 (same dom0):

# iperf -c 192.168.122.49 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.122.49, TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  5] local 192.168.122.144 port 64178 connected with 192.168.122.49 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec  2.57 GBytes  2.21 Gbits/sec
[  4] local 192.168.122.144 port 5001 connected with 192.168.122.49 port 45773
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec  2.66 GBytes  2.29 Gbits/sec

--
Fajar
 
Ok more thorough numbers..

Dom0 = CentOS 5.3 x86_64, DomU CentOS 5.3 x86_64

DomU to DomU

iperf -c 192.168.1.140 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.1.140, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  5] local 192.168.1.139 port 38128 connected with 192.168.1.140 port 5001
Waiting for server threads to complete. Interrupt again to force quit.
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec  2.44 GBytes  2.10 Gbits/sec

iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.140 port 5001 connected with 192.168.1.139 port 38128
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec  2.44 GBytes  2.10 Gbits/sec
------------------------------------------------------------
Client connecting to 192.168.1.139, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.140 port 47926 connected with 192.168.1.139 port 5001
write2 failed: Broken pipe
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0- 0.0 sec  15.6 KBytes    387 Mbits/sec
-----------------------------------------------------------------------------------------------------------------------------

Dom0 to DomU

iperf -c 192.168.1.140
------------------------------------------------------------
Client connecting to 192.168.1.140, TCP port 5001
TCP window size: 26.6 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.254 port 55458 connected with 192.168.1.140 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  1.04 GBytes    893 Mbits/sec


iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.140 port 5001 connected with 192.168.1.254 port 55459
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec  1.02 GBytes    878 Mbits/sec


I'm also noticing that numbers in the 800-900 Mbit range is consistant for Dom0-DomU traffic. Numbers in the 2.5Gbit range is consistant for traffic one way in DomU-DomU. When I get the low numbers 200-350Mb it's also saying write2 failed: broken pipe. Maybe something is not right somewhere.

Grant McWilliams

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