[Twisted-Python] epoll reactor problems

Alec Matusis matusis at matusis.com
Wed Apr 11 16:01:34 EDT 2007

We have tested the upgrade to 2.5 on our dev and stage, and we have not run into this problem. So the only way I know how to demonstrate it is to look on live. We are in San Francisco. I wonder if anybody from Twisted is in the Bay Area, then maybe we can get together, ssh into the live servers and examine it.

Otherwise, I will have to look into  creating a simpler load testing environment with fake clients: this would take me a bit of time…

From: twisted-python-bounces at twistedmatrix.com [mailto:twisted-python-bounces at twistedmatrix.com] On Behalf Of glyph at divmod.com
Sent: Wednesday, April 11, 2007 12:28 PM
To: Twisted general discussion
Subject: RE: [Twisted-Python] epoll reactor problems

On 06:38 pm, matusis at matusis.com wrote:

>I wonder if we should revert to Twisted 2.2 ASAP

I can't speak to your deployment requirements, but it sounds like this inquiry could lead to some extremely valuable information to fix this issue in the next release of Twisted.  Would it be possible to replicate this issue with your application in some kind of load-testing environment so that we can analyze it "in the lab"?  Although I'd really like to see this through to a satisfying conclusion, I don't want your application to have to pay the cost of fixing Twisted.

More information about the Twisted-Python mailing list