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
