From: benny <listen@...>
Date: 2005-04-25T04:54:30+09:00
Subject: Re: apache /fcgi: prevent starting of multiple fcgi processes

Saynatkari wrote:

> 
> Le 24/4/2005, "benny" <listen@marcrenearns.de> a �crit:
>>benny wrote:
>>
>>> hi,
>>>
>>> I am using ruby-fcgi (http://sugi.nemui.org/prod/ruby-fcgi/) with apache
>>> 1.3x.
>>>
>>> under heavy load, apache begins to start other processes of my
>>> fcgi-script. since I am caching some basic code in this main process, I
>>> want every request to be handled by the same fcgi-script.
>>
>>errr! meant to say "I want every request to be handled by the same
>>*process*"
> 
> Apache directives should do the trick:
> 
> FastCgiServer -processes 1
> FastCgiConfig -minProcesses 1 -maxProcesses 1
> 
> See http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html
> 

in case, anyone other should need it:
the complete syntax is (apache 1.3.x)

<IfModule mod_fastcgi.c>
        FastCgiServer /path/to/script.fcgi -processes 1
        FastCgiConfig -minProcesses 1 -maxProcesses 1 -processSlack 1
</IfModule>

> I assume you have some state you are trying to maintain?
> In general, I would have to waggle my finger in warning
> against such practice :)
why? its simply that I have build a framework around the fcgi-script and
want to avoid this framework to be reloaded. In fact this was propagaded as
advantage of fastcgi: that a script doesn't have to be loaded on each
request.

my framework got so large that I don't want it so be several times in RAM.

but I am very interested to hear what disadvantages this configuration might
have to me.
is it simply an issue of threads-performance vs. RAM overhead? 

benny