[Twisted-Python] Degrading under load

[Itamar Shtull-Trauring]

On Thu, 2006-03-09 at 13:49 -0800, Alec (Chatango) wrote:

> I should add here that in our case, the load was driven not by
> connection/disconnection events, but by the number of established
> connections. When that number was in the vicinity of 5000, system poll()
> became very slow (we run poll reactor).

An epoll-based reactor would probably help significantly in this case.
Also note that Twisted 2.x had some algorithmic speed improvements over
1.3 and should scale better (though that doesn't help with poll() being
a bottleneck).