[EMAIL PROTECTED] wrote:
>Modperlers...,
>
>I'd like to start a discussion about the deficiences in Apache/modperl
>and get you feedback with regard to this issue. The problem as I see
>it is that the process model that Apache uses is very hard on modperl.
>It is very memory inneffecient basically. Each process of apache has
>it's registry which holds the compiled perl scripts in..., a copy of
>each for each process. This has become an issue for one of the
>companies that I work for, and I noted from monitoring the list that
>some people have apache processes that are upwards of 25Megs, which is
>frankly ridiculous.
1) Are you preloading the scripts with RegistryLoader? That puts them in the
parent process, so the memory will be shared by the children. Each child will
still [seem to] be 25 megs, but the children will have a lot of overlap.
2) Are you using the two-server model, backend & frontend? It's a must if you
want to make efficient use of your memory.
3) If you're already doing these things and you still aren't satisfied, perhaps
mod_perl isn't for you and you want to look at FastCGI or a similar project.
I've never had occasion to use it. You'll no longer have access to the Apache
API, but it sounds like you're not using that anyway.
------------------- -------------------
Ken Williams Last Bastion of Euclidity
[EMAIL PROTECTED] The Math Forum
