Greg Stark wrote:
>
> A lot of people have talked about running a proxy in front of your mod_perl
> processes, well a word of caution, maybe squid is more efficient, but
> mod_proxy does a double fork at the end of every request. This is part of the
> caching file garbage collection but it happens even if you don't have caching
> enabled.
>
> I'm trying it with the second to last line of src/modules/proxy/proxy_http.c
> commented out, and it seems to be ok after about an hour.
>
> This should maybe be mentioned in the mod_perl guide with the mod_proxy
> recipe.
>
Someone already reported this double fork problem on the list,
and submitted a patch to mod_proxy, and I was able to get it
shortly thereafter from the apache CVS. It should be rolled
into the latest apache sources. The latest source this problem
seemed to affect was 1.3.6.
w/o the double fork problem, I notice about a 20% performance
hit when pulling content through the proxy.
-- Joshua
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NODEWORKS >> free web link monitoring Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
