[Twisted-Python] Stackless Twisted shocking performance

[Travis Kiel]

Simon,

This is a shot in the dark, but have you tested the twisted performance with the nagle algorithm disabled?
 
Travis W Kiel

-----Original Message-----
From: twisted-python-bounces at twistedmatrix.com [mailto:twisted-python-bounces at twistedmatrix.com] On Behalf Of Jean-Paul Calderone
Sent: Sunday, March 22, 2009 4:35 PM
To: Twisted general discussion; stackless at stackless.com
Subject: Re: [Twisted-Python] Stackless Twisted shocking performance

On Sun, 22 Mar 2009 18:32:30 -0500, Jean-Paul Calderone <exarkun at divmod.com> wrote:
>On Fri, 20 Mar 2009 18:16:47 +0000, Simon Pickles <sipickles at googlemail.com> 
>wrote:
>>[snip]
>>
>>As more updates are sent zone->hub, per second, the incoming 
>>client->hub->zone messages take SECONDS to get thru! This is with approx 50 
>>messages per second between a single zone and the hub.
>
>"message" is a very non-specific unit of message.  For example, I just

Ahem, excuse me.  Unit of *measure*. :)

>threw together a PB demo that does 1754 messages per second.  That's a
>lot more than your 50/sec, but who knows why?  You'll need to narrow down
>the bottleneck a bit more precisely before there's much chance of getting
>rid of it.
>
>Jean-Paul
>
>_______________________________________________
>Twisted-Python mailing list
>Twisted-Python at twistedmatrix.com
>http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>

_______________________________________________
Twisted-Python mailing list
Twisted-Python at twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Notice: This communication, including attachments, may contain information that is confidential. It constitutes non-public information intended to be conveyed only to the designated recipient(s). If the reader or recipient of this communication is not the intended recipient, an employee or agent of the intended recipient who is responsible for delivering it to the intended recipient, or if you believe that you have received this communication in error, please notify the sender immediately by return e-mail and promptly delete this e-mail, including attachments without reading or saving them in any manner. The unauthorized use, dissemination, distribution, or reproduction of this e-mail, including attachments, is prohibited and may be unlawful. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail and the attachments (if any).