Re: [squid-users] squid exceptionally slow to forward when direct is not possible

Hunter Fuller wrote:
> The setup I currently have is that I am forwarding all my requests to
> a machine that runs Privoxy. This Privoxy has a live net connection
> 24/7. At midnight, the "direct" net connection goes out. This Privoxy
> is still up, though. When the direct net connection is down, squid
> takes nearly forever to forward requests to Privoxy. As in, 5 or 10
> minutes. Once the page begins loading, though, the rest of the page
> loads practically instantly. The problem resolves itself when the
> direct net connection comes back alive in a couple of hours.
>
> I know this is not a Privoxy problem; Privoxy responds instantly all the time.
>
> What could be causing this? One of the strangest problems I've seen...
>

http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#head-f7c4c667d4154ec5a9619044ef7d8ab94dfda39b

Effectively Squid doesn't use cache_peers for content that is likely
non-cacheable unless "forced". Alternatively you could be using dst
acls or something else that requires DNS lookups.

> -hackmiester
>

Chris
Received on Tue Mar 24 2009 - 19:41:26 MDT