Another drawback of this approach is that when serving output to a
client with a slow connection, the huge mod_perl-enabled server
process (with all of its system resources) will be tied up until the
response is completely written to the client. While it might take a
few milliseconds for your script to complete the request, there is a
chance it will still be busy for a number of seconds or even minutes
if the request is from a client with a slow connection. As with the
previous drawback, a proxy solution can solve this problem.
We'll discuss proxies more later.
Proxying dynamic content is not going to help much if all the clients
are on a fast local net (for example, if you are administering an
Intranet). On the contrary, it can decrease performance. Still,
remember that some of your Intranet users might work from home
through slow modem links.