Re: caching web traffic
On Mon, 24 Jan 100, Allen Ahoffman wrote:
> I'm in a bind, and its not a name server.
> Have 2 t1's t3 is late.
> I am considering putting up temporarily a web cache on other end of lines.
> I need to know how the redirect process works.
> e.g. how do I redirect the requests to the cache.
> Thi is not internal people web surfing, rather we have web servers here
> and want to cache them on other end of line.
you could set up a small array of squid caches, throw all your webservers
on a private IP block behind the squids, let the squids resolve the
private space webservers through the host file or an internal nameserver.
Use ns to point the rest of the world at the caches instead of directly at
the web servers.
> Also, whats anyone's impression of the Cobalt CacheRaq.
Haven't used them, but have tested NetApp's NetCache -- we used an atm
switch to do transparent caching for a commercial IP network by
redirecting all port 80 traffic. The NetApp worked admirably. I see no
reason why squid on an Alpha wouldn't do just as well, though, at a
fraction of the price.
> Also, any hardware recommendations would be nice.
> And, reasonable experience with how much it might save on the line use.
Fast CPU's, and the fastest disk subsystem you can lay your hands on. I'm
bias'd towards the Alpha Processor and IBM disks in hardware raid configs.
> We have 2 large sites which can probably get significant amounts of
> savings from the cache server, but it might need a lot of disk space, but
> htats not a big deal really.
caching works well, in general. Every site will have users that complain,
in my experience. Keep your ear to the ground and put the appropriate spin
on it for your users.
Brian
fade@etc.etc.etc.
How often I found where I should be going only by setting out for
somewhere else..
-- R. Buckminster Fuller
Reply to: