Mohammed Rashad <[email protected]> wrote on 16.03.2011 09:51:56:
> So what you are saying is its good to have "unused" processes. what
> is the need?
> How it is beneficial
The whole point of FastCGI is to have a long running process that does not
have the
startup delay that a CGI program has (compilie time in interpreted
languages,
loading libraries, opening database connections, ...)
A started FastCGI application has done all these things already when the
first
request comes in. besides that it almost behaves like a CGI application.
That's why the technique got the term FastCGI.
Depending on the load of a web server and combined with todays browsers
spikes in the amount of requests per timeframe are common nowadays. That's
why
you have to provide enough resources to handle those spikes. The way to do
this
in FastCGI is to have many FastCGI processes running idle ("unused").
Apache does the same thing - have a look at the MinSpareServers and
MaxSpareServers
setting in the mpm_prefork_module.
Regards,
Frank
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
