Re: CARP for squid 1.2

Hi Eric,

In the case as you described below, what kind of configuration should the
CARP server (redirector) actually have. I guess not a lot of memory and
harddisk space, but a lot of file-descriptors ??

Hope you can advise.

Walter Klomp,
Systems Manager / Administrator (Internet)
Swiftech Automation Pte. Ltd.
25 Kallang Avenue #03-01, Kallang Basin Ind. Est.
Singapore 339416
Tel. 274 4722 ext. 104 - Fax. 274 4966
e-mail: walter@swiftech.net.sg
http://www.swiftech.net.sg
===========================================================
Swiftech Internet, the Value Added Service Provider with a personal touch.
===========================================================

-----Original Message-----
From: Eric Stern <estern@packetstorm.on.ca>
To: squid-users@nlanr.net <squid-users@nlanr.net>
Date: Monday, June 01, 1998 1:22 AM
Subject: CARP for squid 1.2

>
>Well, I just whipped up a patch to add CARP to squid 1.2. You can get it
>from http://www.mgl.ca/~estern/squid-1.2-carp.patch.
>
>Not sure what CARP is? I'll include a bit of the README here.
>
>Well, Microsoft actually went and developed something cool and useful
>for a change. CARP (Cache Array Routing Protocol) intelligently divides
>load
>up between a number of proxy servers. This patch adds CARP support to
>squid.
>
>A squid running CARP is intended to be a "front end" for 1 or more other
>cache servers. It accepts requests, and then retrieves the objects from
>the caches sitting behind it. A CARP squid does not need to cache anything
>itself (and probably shouldn't).
>
>I quote the Abstract from the CARP White Paper (Copyright Microsoft Corp.)
>
>Microsoft Proxy Server 2.0 uses the Cache Array Routing Protocol (CARP) to
>provide seamless scaling and extreme efficiency when using multiple proxy
>servers arrayed as a single logical cache. CARP uses hash-based routing
>to provide a deterministic "request resolution path" through an array of
>proxies. The request resolution path, based upon a hashing of proxy array
>member identities and uniform resource locators (URLs), means that for any
>given URL request, the browser or downstream proxy server will know
>exactly
>where in the proxy array the information will be stored - whether already
>cached from a previous request, or making a first Internet hit for
>delivery
>and caching.
> CARP provides two powerful benefits:
> 1) Because CARP provides a deterministic request resolution path,
>there
>is none of the query messaging between proxy servers that is found with
>conventional Internet Cache Protocol (ICP) networks, a process that
>creates
>a heavier congestion of queries the greater the number of servers.
> 2) CARP eliminates the duplication of contents that otherwise occurs
>on
>an array of proxy servers. With an ICP network, an array of five proxy
>servers
>can rapidly evolve into essentially duplicate caches of the most
>frequently
>requested URLs. The hash-based routing of CARP keeps this from happening,
>allowing all five proxy servers to exist as a single logical cache. The
>result
>is a faster response to queries and a far more efficient use of server
>resources.
>
>/-----------------------------------------------------------------------/
>/ Eric Stern - PacketStorm Technologies - (519) 837-0824 /
>/ http://www.packetstorm.on.ca /
>/ WebSpeed - a transparent web caching server - available now! /
>/-----------------------------------------------------------------------/
>
>
Received on Mon Jun 01 1998 - 03:05:34 MDT