httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Behlendorf <>
Subject Re: Apache + mod_perl on Solaris
Date Fri, 01 Aug 1997 00:56:12 GMT
At 11:15 AM 7/31/97 -0700, Paul Phillips wrote:
>Taking some measure along these lines is strongly recommended,
>even if memory isn't an issue.  We had some pretty serious performance
>problems with apache+mod_perl on ultra-2's with 256MB until we moved
>image serving to another server running zeus (don't shoot me.) Our
>httpd binaries are 4.5 MB stripped, so you can imagine that process
>creation is expensive.  Much better to let mod_perl do mod_perlish

On that note; when running the Java web server was the only scalable way to
do java server-side, we used the proxy module to forward requests matching
certain characteristics (i.e. <Location *.jtml>) on to the Java server.
This worked pretty well, but the mod_jserv solution I'm sure will be
faster.  I bring this up because maybe there's a need for generalizing the
wire protocol between mod_jserv and the java VM, into something that could
be, for example, a perl engine running on the backend; that way a process
just serving images wouldn't be bogged by the memory perl takes up.


"Why not?" - TL  - -

View raw message