[Twisted-Python] 100% CPU on high opened descriptors

Ray Cote rgacote at appropriatesolutions.com
Tue Apr 26 16:34:09 EDT 2011


----- Original Message -----
> From: "Luke Marsden" <luke-lists at hybrid-logic.co.uk>
> To: "Twisted general discussion" <twisted-python at twistedmatrix.com>
> Sent: Tuesday, April 26, 2011 2:08:40 PM
> Subject: Re: [Twisted-Python] 100% CPU on high opened descriptors
> On Tue, 2011-04-26 at 17:42 +0200, Juan Antonio Ibañez Santorum wrote:
> > Hello!
> >    I have a Linux box serving my twisted app. All works ok except
> > after some days running (where I can see my CPU going to 100%). I
> > saw
> > that CPU goes 100% usage when the app reaches to 1024 opened
> > descriptors (sockets).

I assume that using a reverse proxy (Apache, nginx, etc.) in front of Twisted removes this problem? 
(or at least displaces it from being Twisted's problem to being the proxies problem.)

Is it recommended to always run Twisted behind a proxy? 
We've been doing that simply to offload delivery to the final client, but I'm thinking it may have a 
more general need.

--Ray



More information about the Twisted-Python mailing list