Re: concurrent connections and multiple accepts

> No.  (A 20 sec. sleep in a CGI sounds strange; CGIs need high throughput.  I'd look at whether you really need to do that.)
sorry should have explained. it is just a test. to see what would happen if for some reason a page took a very long time.


OK. I clearly need to do some reading and testing.

Thanks Tim


Tim Wood wrote:

>At 01:27 AM 06/17/05, Barclay Curtis wrote:
>  
>
>>>FCGI provides for multiple concurrent instances of the FCGI app., adding processes as load goes up
>>>      
>>>
>>Do I have to code something specific to get fast cgi to add processes?
>>    
>>
>
>No, just configure it in httpd.conf.  It's all documented.
>
>  
>
>>Currently:
>>If I have only one instance (child) of my FCGI appserver running (so effectively one fcgi external server) and I look at page A
>>on my site which has a 20 second sleep in it. Then I look at page B (which is just a normal kinda page, no delays).
>>Page B wont load until page A has finished. Does this not mean that they are using the same process?
>>    
>>
>
>No.  (A 20 sec. sleep in a CGI sounds strange; CGIs need high throughput.  I'd look at whether you really need to do that.)
>
>  
>
>>How does FCGI determine when it needs to add a new process?
>>    
>>
>
>Roughly, if all the current processes are busy. i.e. are running within the accept() loop, the process manager starts a new one, up to a configured limit.  RTFM.
>
>TW
>
>
>  
>

-- 
Barclay Curtis
Senior Developer
 
Nexus Media Communications Ltd
Media House, Azalea Drive, Swanley, Kent BR8 8HY
_____________________________________________
+44 (0) 1322 611460
www.nexusmedia.co.uk

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/