Its not strictly true that mod_perl is handling the static content, it actually only handles those resources that it is configured to handle, however the mod_perl will be loaded for every new apache process that is forked to handle a request whether the mod_perl will be used in the processing of the request or not, now because an apache with mod_perl has a larger memory footprint than one without it , if you are serving more static content than that handled by mod_perl you are going to get a lot of large processes which don't really need to be that big. To this end some people will run an apache without mod_perl on port 80 to serve the static content and a second one with mod_perl to serve the dynamic content - the first proxying the requests to the second where appropriate. Of course if the server is only moderately loaded (in terms of it's free memory, swap usage and so forth) you probably won't even notice much difference if you have a mnod_perl apache serving your static content or not.
With Apache 2.0 and mod_perl in a threaded configuration the effects of the mod_perl loading can be mitigated by the use of "interpreter pools" whereby the perl interpreter is requested from a pool when mod_perl handles the request.
/J\
In reply to Re: mod_perl without separate config for static HTML?
by gellyfish
in thread mod_perl without separate config for static HTML?
by gunzip
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |