Re: how to break out of FCGX_Accept_r - multi-threaded fastcgi performance

Hi,

We do not experience any serious delays, certainly not of 3 seconds, 
which is unexceptable in a production environment.

Greets,

Andrej



Jack wrote:

>Hello,
>
>If you need to recycle the fastcgi processes, using a counter
>is much easier than a timer. I know this doesn't really answer
>Andrej's question :)
>
>I have another question though. I'm glad to see lots of replies
>to the question. I suppose many people are using multi-threaded
>fastcgi servers because FCGX_Accept_r() is the thread-save version
>of FCGX_Accept(). Or, do most people just use FCGX_Accept_r()
>in single-threaded fastcgi servers?
>
>Anyway, I have a question for the multi-threaded fastcgi developers.
>I tested the multi-threaded sample and experienced very poor
>performance. Each request takes about 3 seconds. I sent an email
>to the list but didn't get any replies. I thought no one was using
>multi-threading :) I also read another earlier post mentioning the
>same 3-second issue with Apache2 + mod_fastcgi. I used lighttpd but
>the symptoms were very similar. So, my question is, are you, the
>multi-threading users, getting good performance? Even with the
>sample that comes with fastcgi? Could there be something that I did
>wrong?
>
>  
>
>------------------------------------------------------------------------
>
>___________________________________
>fastcgi-developers mailing list
>http://fastcgi.com/fastcgi-developers/
>  
>
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/