Am Fr, 28.01.2011, 09:31, schrieb Michiel Beijen:
On Fri, January 28, 2011 01:14, Michael Peters wrote:
Another thing that maybe the OP should look at (if he hasn't already) is
to run a proxy in front of the main mod_perl application. Even if the
proxy is on the same machine it will help because you can reduce the
number of memory-heavy mod_perl processes/threads and handle the same
number of connections.
I have read that advice before; then it was because of this bug concerning
running mod_ssl + mod_perl at the same time on Win32:
https://issues.apache.org/bugzilla/show_bug.cgi?id=36751
Unfortunately the bug still exists but the bug report was set to invalid
because it did not get proper attention.
What would be the best (windows-style) way of running a proxy in front of
apache?
Insights are welcome!
--
Mike
(Linux-style) I use nginx and it works great (by coping with ssl and
keep-alives) whether you allow it to cache requests or not. It can serve
thousands of simultaneous connections and still has just a memory
footprint of a few mb. I dont know if the event-model works as great under
windows but there are windows builds available on the website
(http://nginx.org) so it should be worth a try.
Hendrik
