[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen Performance


  • To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • 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
  • 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=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.