[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: Tue, 13 Oct 2009 10:54:37 -0700
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 13 Oct 2009 10:55:46 -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=Sp2WiCA37FtK6TqxLVOooqJS1TiiE0Pgz7SN4ILbvOtGbFxmdI+5LV62l2EbioanVh Ns075CZ4nEOzXhoQN0g4lfJDQ65aX15nX1IdHKJmb6fViokk6QB8fLq0WC5ra8nGMM0E MSrNnhaMdcV9FZTIlMBLrpzocHuTEqLulBFVg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Tue, Oct 13, 2009 at 5:06 AM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
On Tue, Oct 13, 2009 at 3:05 PM, Grant McWilliams
<grantmasterflash@xxxxxxxxx> wrote:
>> [ ID] Interval    Transfer   Bandwidth
>> [ Â4] Â0.0-10.0 sec Â1.57 GBytes Â1.35 Gbits/sec
>>
>> This is on a 2.4GHz Opteron 2378. Since domU <-> domU transfer are
>> mostly CPU-bound, faster CPUs should yield higher performance.

>
> Thanks for the numbers I reran iperf tests and this is what I got on xen
> 3.4.1. This is on an 8 core Intel system with 16GB ram.
>
> DomU to DomU - 2.0 Gbits/sec
> DomU to Dom0 - 3.46 Gbit/sec
> Dom0 to DomU - 346 Mbits/sec
>
> These are similar ratios that I got before but because this system is about
> 3x faster than the old system the numbers are bigger. Fajar, if you get time
> could you see if you see something similar on your system?

That's odd. I'll see if I can get a test Intel box tomorrow to compare
the numbers. In the mean time, what does your environment look like?
64bit? what distro and kernel version?

If possible, can you test installing RHEL/Centos 5.4 64bit dom0 and
update to Gitco's Xen 3.4.1? That's what my setup mostly like, and so
far network performance (including domU <-> domU) Âhas been great.

--
Fajar

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


A third system running CentOS 5.3 Dom0, Ubuntu 9.04 DomU with Debian Lenny xenified kernel and CentOS 5.3 DomU. Ghz Core2 Duo (2.2 Ghz)

DomU to DomU - 2.89 Gbit/sec
DomU to Dom0 -Â 4.4 Gbit/sec
Dom0 to DomU -Â 257 Mbits/sec

None of these summaries are really that accurate because if I do an iperf -c 192.168.0.100 -r the return speed is always in the toilet.

Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[Â 4] local 192.168.0.191 port 5001 connected with 192.168.0.196 port 57543
[ ID] IntervalÂÂÂÂÂÂ TransferÂÂÂÂ Bandwidth
[ 4] 0.0-10.0 sec 3.38 GBytes 2.89 Gbits/sec
------------------------------------------------------------
Client connecting to 192.168.0.196, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[Â 4] local 192.168.0.191 port 38701 connected with 192.168.0.196 port 5001
write2 failed: Broken pipe
[ ID] IntervalÂÂÂÂÂÂ TransferÂÂÂÂ Bandwidth
[ 4] 0.0- 0.0 sec 15.6 KBytes 343 Mbits/sec


This is the behavior I observed almost 2 years ago and it still seems to be consistant. Fajar, if you could run these on your systems to see if you're seeing something different. The one thing that's always the same is that I'm using CentOS 5.3 as a Dom0.


Grant McWilliams

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

_______________________________________________
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®.