Date: Fri, 26 Mar 1999 07:13:05 -0800 (PST) From: <jfesler@gigo.com> To: Stuart Henderson <stuart@eclipse.net.uk> Cc: Steve Price <sprice@hiwaay.net>, freebsd-isp@freebsd.org, hamellr@dsinw.com Subject: Re: Need help fine-tuning a web server (fwd) Message-ID: <Pine.BSF.4.00.9903260706250.1482-100000@heaven.gigo.com> In-Reply-To: <36FBA273.F6108F6B@eclipse.net.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Anyone have any experience setting up a heavily-loaded web > > server box that can spare a few answers to this gentleman's Additionally, for the database: if it is a *heavilly used* database CGI application, then see about making the CGI persistant. - Perl apps can be _tremendously_ helped with mod_perl http://perl.apache.org . - Simple C code, can be turned into Apache modules. More complex CGI, can possibly benefit from "fastcgi" which keeps any CGI app persistant, and tunnels data from the web server to the CGI. Persistance will buy you lots of things: - No load/exec time of the CGI - No "fork" penalty as the httpd splits off to run the cgi - Database handles don't have to be reopened constantly 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. One thing to keep in mind: Every case is different :-). A critical analysis of the true needs is crucial to finding the right solution. This is independent of the choice of OS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.00.9903260706250.1482-100000>