Re: [TCLUG:18516] Squid as an httpd-accelerator

[Troy Johnson <john1536@tc.umn.edu>]

Timothy Wilson wrote:
> On Thu, 1 Jun 2000 andy@theasis.com wrote:
> > To speed up browsing, you can cache on disk pages that are often retrieved
> > -- this is good for providing improvements to common sites, say, for
> > multiple hosts on the LAN. Even sites that change their content often will
> > keep using certain elements, such as logo .gifs, or menu frames.
> Sure, this makes sense. Reduce traffic over the Internet.
> > If you're trying to speed up your server, you can cache common pages in
> > RAM, so that they don't have to be read from disk when requested.
> Apache doesn't use RAM for this by itself? If not, then I understand where
> Squid would come in handy. I had always assumed that all that RAM people
> recommend for Web servers would be used as apache "cache."

I think the RAM is for the many copies of Apache httpd deamons forked
off to deal with incoming requests, not to cache anything. Squid is made
for caching, wether from RAM, or from a nicely organized cache on disk.
It doesn't have to make any of the difficult decisions Apache has to
make, just serve it or get it. But you will get the most milage, I
assume, from Squid in combination with an Apache daemon heavily laden
with modules.

-- 
	<a href="http://umn.edu/~john1536">Troy Johnson</a>

Government is actually the worst failure of civilized man. There has
never been a really good one, and even those that are most tolerable
are arbitrary, cruel, grasping and unintelligent.
	-- H. L. Mencken