Fwd: Re: Beginners Question

On Wednesday 12 July 2006 16:37, Jose Adriano Baltieri wrote:
>  Chris Lightfoot wrote:
>
> -- rather than having lots of threads, you can just have
> the webserver spawn lots of copies of this. Slightly less
> efficient, maybe, but much quicker to get up and running
> and much easier to debug.
>
> I need to understand it better...
>
> Considering the single-threaded model, some more questions :
>
> If I have 100 simultaneous requests, I'll have 100 copies of FASTCGIs
> loaded ?

It depends on your FastCGI configuration. Well written c-app can handle 800
requests per second or even more (also depends on your hardware) ;) So, there
will be one single fastcgi child working on them.

As soon as it is not capable of handling them, Parent process spawns more
childs but upto MAX (defined in the FastCGI config)

> In my case, the 100 FASTCGI will be a copy (or a clone) of a simple one
> that only dumps the file and waits the answer. When will they end ? That
> is, when they will exit ?

After having fulfilled request, after some time (TIMEOUT) they (extra
processes) will be killed by the parent process

> Obrigado,
> ---------------------------------------------------------------------------
>--- Jose Adriano Baltieri - Analista de Sistemas
>                 DTI - CENTRO - UNIMEP - Universidade Metodista de
> Piracicaba PIRACICABA - SP - Brasil - Fone : (19) 3124-1858
> ---------------------------------------------------------------------------
>---

Cheers,
j.

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