Re: multiple outgoing addresses

On Wed, 28 Oct 1998, Andrew Cormack wrote:

> On Tue, 27 Oct 1998, Henrik Nordstrom wrote:
>
> > > 2. I'm looking for a way how to use different tcp_outgoing_address
> > > based on client acl, something like that:
> >
> > This is sort of possible. What you can do is to set up no-caching Squids
> > that binds to the intended outgoing address, and use cache_peer_access
> > and never_direct to direct requests to the correct outgoing address.
>
> I'd thought of this a while ago, as I'm being asked to account separately
> for cache traffic from two different sites. I didn't try it, as I was
> concerned about the additional load the duplicate squid process would
> place on the machine. If anyone is running two squids on one machine, I'd
> be grateful for your estimates of how much extra load this places on the
> machine, over sending the same number of requests through a single
> process. Presumably, since the second squid process isn't maintaining a
> cache directory, its memory requirements stay pretty low, but how much do
> the two processes fight over other system resources ?
>
> Thanks for any information, or just reassurance that it can work!
>
Hi,

well, I've tried and.. it works!
I didn't notice so much extra load, maybe because our machine is dual
PentiumII/350 with 512 megs of RAM ;)
Main squid has 64M cache-mem and 6GB cache-dirs total, 2nd squid has 2M
cache-mem and 1M cache-dir. I don't know how to tell squid there is no
cache-dir. Directives "cache-dir none" or "cache-dir /any 0 1 1" don't work,
so I used "cache-dir /any 1 1 1".

David Trcka, PODA s.r.o., Havirov, CZ
network administrator/spravce site
          ICQ#: 24079192
Received on Sun Dec 06 1998 - 11:34:47 MST