From owner-freebsd-isp Fri Mar 26 10:24:49 1999 Delivered-To: freebsd-isp@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 2DE061554B for ; Fri, 26 Mar 1999 10:24:45 -0800 (PST) (envelope-from fanf@demon.net) Received: by noc.demon.net; id SAA11740; Fri, 26 Mar 1999 18:24:26 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma011721; Fri, 26 Mar 99 18:24:23 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10QbHL-00041Y-00; Fri, 26 Mar 1999 18:24:23 +0000 To: isp@freebsd.org From: Tony Finch Subject: Re: Need help fine-tuning a web server (fwd) In-Reply-To: References: <36FBA273.F6108F6B@eclipse.net.uk> Message-Id: Date: Fri, 26 Mar 1999 18:24:23 +0000 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org wrote: > >- Perl apps can be _tremendously_ helped with mod_perl > http://perl.apache.org . If you don't trust the perl enough to run it in the server (e.g. customer scripts on a shared server) you can improve exec time a lot by statically linking perl. >Now, if most of your content is static, the above won't buy you much and >possibly hurt (memory-wise) ;-). The previous comment of a proxy front >end is especially useful - it will know the difference between static >content and dynamic content, and only invoke use of the heavier httpd's as >needed. Yep. And with a bit of hacking you can use a reverse proxy to spread the load or even have special-purpose back-end servers. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message