rder-left:1px solid rgb(204,204,204);padding-left:1ex">

> This costs memory, and all the more since many perl modules are not th=
read-safe, so if you use them in your code, at this moment the only safe wa=
y to do it is to use the Apache httpd prefork model. This means that each A=
pache httpd child process has its own copy of the perl interpreter, which m=
eans that the memory used by this embedded perl interpreter has to be count=
ed n times (as many times as there are Apache httpd child processes running=
at any one time).



This isn=E2=80=99t quite true - if you load modules before the process fork=
s then they can cleverly share the same parts of memory. It is useful to be=
able to "pre-load" core functionality which is used across all f=
unctions {this is the case in Linux anyway}. It also speeds up child proces=
s generation as the modules are already in memory and converted to byte cod=
e.



One of the great advantages of mod_perl is Apache2::SizeLimit which can blo=
w away large child process - and then if needed create new ones. This is no=
t the case with some of the FCGI solutions as the individual processes can =
grow if there is a memory leak or a request that retrieves a large amount o=
f content (even if not served), but perl can't give the memory back. So=
FCGI processes only get bigger and bigger and eventually blow up memory (o=
r hit swap first)











--

=C2=A0The Wellcome Sanger Institute is operated by Genome Research

=C2=A0Limited, a charity registered in England with number 1021457 and a r>
=C2=A0company registered in England with number 2742969, whose registered <=
br>
=C2=A0office is 215 Euston Road, London, NW1 2BE.