Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id SAA29720; Thu, 31 Jul 1997 18:31:46 -0700 (PDT) Received: from brianb.organic.com (localhost.hyperreal.org [127.0.0.1]) by hyperreal.org (8.8.5/8.8.5) with SMTP id SAA29704 for ; Thu, 31 Jul 1997 18:31:42 -0700 (PDT) Message-Id: <3.0.3.32.19970731175612.008e1860@localhost> X-Sender: brian@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 31 Jul 1997 17:56:12 -0700 To: new-httpd@apache.org From: Brian Behlendorf Subject: Re: Apache + mod_perl on Solaris In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org 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 >things. 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. ) 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. Thoughts? Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- "Why not?" - TL brian@organic.com - hyperreal.org - apache.org