Re: [squid-users] Streaming is killing Squid cache

Brett Glass wrote:
> Amos:
>
> We've discovered that Squid won't cache Windows Update unless we set
> quick_abort_min to -1. This is because Windows update fetches subranges,
> and the subrange fetches individually aren't enough to get the updates
> cached. Ideas?

Leaving min at -1, and max at something large (10-50MB?)

Should abort the streams when they reach the max value, You'll have to
set the max to something reasonably higher than the WU cab size.
Service Packs may cause issues since they are >100MB each, but are
infrequent enough to use a spider and cause caching if need be.

Amos

>
> --Brett Glass
>
> At 08:41 PM 2/28/2009, Amos Jeffries wrote:
>
>> Brett Glass wrote:
>>> Everyone:
>>> This past week, we've had multiple events where Web browsing slowed to a crawl and we discovered that our transparent Squid cache had very high CPU loads (sometimes completely saturated). We investigated, and saw that the cache was downloading streams from sites such as "totalstream.net". Even after we turned off transparent caching at the router, the cache continued to download the stream, leading us to believe that the cache is trying to eat the entire stream even after the requesting user has gone away. Have others seen this problem? Will we have to disable transparent caching due to problems with streaming?
>>> --Brett Glass
>> Check your quick_abort_* settings.
>> http://www.squid-cache.org/Doc/config/quick_abort_max/
>> http://www.squid-cache.org/Doc/config/quick_abort_min/
>> http://www.squid-cache.org/Doc/config/quick_abort_pct/
>> and
>> half_closed_clients off
>>
>> They can be set to cause squid to either finish fetching objects after the client is gone, or abort when the client goes away.
>>
>> Amos
>> --
>> Please be using
>> Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>> Current Beta Squid 3.1.0.5
>

-- 
Please be using
   Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
   Current Beta Squid 3.1.0.5