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/
Home Products Support Community News


RE: [Xen-users] Bad TCP accept performance

To: "Russ Purinton" <rpurinton@xxxxxxxxxxxxxxxxxxxxxxx>, Carl Byström <cgbystrom@xxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>
Subject: RE: [Xen-users] Bad TCP accept performance
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Thu, 26 May 2011 00:56:23 +1000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 25 May 2011 07:58:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <37A3FE5EB8938A499D07FA505DD32ED2BEFA75@xxxxxxxxxxxxxxxxxxxxxxx>
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: <BANLkTimRM22jKtC6Qrv_PsDo-3LbSMtarQ@xxxxxxxxxxxxxx><20110523202257.GD32595@xxxxxxxxxxx><BANLkTim68TbZLrCVZcK8VWQxErYHkC56vA@xxxxxxxxxxxxxx> <37A3FE5EB8938A499D07FA505DD32ED2BEFA75@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwaXAC6uri6etW+StKK5AgVga3p6wAhbANQAAJ7M0A=
Thread-topic: [Xen-users] Bad TCP accept performance
> How well performs however is kind of a moot point however as no real
> application would make use of this.  The real test is how many you can spin up
> from a physical host outside of the virtualization platform.   There's also
> value in knowing how many you can make from VM to VM.

It does reduce the scope of the test to the TCP/IP stack though. If 
performs well then the test doesn't tell you much, but if performs 
badly then it definitely tells you where you should be looking for the problem, 
or at least it tells you that you shouldn't be looking for problems in the 
DomX<->DomX layer.


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>