Re: [squid-users] more delaypool woes

Solution was a lot easier than I thought.

squid-accel has 100% cache misses, so we moved the delaypool
there. Now even downloading the same file back-to-back
goes through the delaypool whether it's cached in squid-maincache
or not. We'll cut off external access to the squid-maincache instance
by simply forcing all traffic to squid-accel via dns.

cheers,
Mike

> I have 2 squid instances on the same machine, different
> ip's; onecacheing, the other redirecting. Users connect to
> either.
>
> squid-accel -> a.b.c.201:80 [no cache, redirect only]
> | >>>> our network<<<>>>internet<<< users
> |
> squirm [redirect program]
> |
> squid-maincache -> a.b.c.200:80
> || >>>>our network<<<>>> internet <<<
> users
> ||
> ||
> content server
>
> Initially I configured squid-maincache to have a delaypool.
> However, delaypools only delays *un-cached* files (and
> indeed this is stated in the documentation). Presumably this
> is because delaypools was designed with incoming rather
> than outgoing traffic in mind?
>
> Sadly this only allows us to shape traffic between the cache and the
> content server. Alas, this is not what we want.
> We want to delay *cached* files with the same specification
> [we really don't like our users ;-) ]
>
> any ideas as to how we might achieve this?
>
> Mike
Received on Thu Aug 02 2001 - 02:35:11 MDT