[FASTCGI] Threaded C fcgiapp implementation problems and questions
onefriedrice at brokenzipper.com
Wed Apr 22 22:32:03 EDT 2009
I have seen weird behavior trying to use a lot of requests (a new one
per connection) versus one request object per thread. While the
problems you're describing are not exactly the problems I've seen, I
wonder if you would see an improvement if you could model your app more
closely with the threaded example.
Jonathan Gray wrote:
> It's not really possible on my application. The connections are
> long-lived and do not reconnect in sync, so there is no instance in time
> where no one is connected. The transition from one web server to another
> would be extraordinarily complex in my case.
> There's obviously something wrong or misconfigured in my application,
> fastcgi, lighttpd, system settings... or most likely the interaction of
> these things. I'd rather not just treat the symptom.
> On Wed, April 22, 2009 5:33 pm, Jon Ribbens wrote:
>> On Wed, Apr 22, 2009 at 04:39:55PM -0700, Jonathan Gray wrote:
>>> This is suspiciously close to 64 * 1024 (what i have set my linux max
>>> file descriptors to). Is lighttpd or fastcgi somehow hanging on to file
>>> descriptors, either to the lighttpd->fastcgi file socket, or http/tcp
>>> sockets? Is there something else tied to ~64k I should look in to?
>> Several things I should imagine. Make your process restart every
>> 60,000 requests?
> FastCGI-developers mailing list
> FastCGI-developers at mailman.fastcgi.com
More information about the FastCGI-developers