[squid-users] Sudden but sustained high bandwidth usage
Amos Jeffries
squid3 at treenet.co.nz
Wed Mar 9 10:49:03 UTC 2016
On 9/03/2016 4:26 a.m., Heiler Bemerguy wrote:
>
> This way it won't cache any "range" downloads as "range_offset_limit 0"
> is the default option and it will make squid only download what the
> client requested.
>
> From squid-cache.org: "A size of 0 causes Squid to never fetch more than
> the client requested. (default)"
>
> What I'm trying to accomplish here, and have done while using AUFS, is
> to make squid CACHE/STORE RANGED REQUESTS for windowsupdate.com, instead
> of its default action of aborting.
>
> How can I monitor whats the reason of all the "TCP_SWAPFAIL_MISS" on
> range downloads like these:
The two details are a little confusing unless you are aware that the 206
is not related to the SWAPFAIL, nor to the MISS.
>
> 1457381845.725 241 10.101.1.23 TCP_SWAPFAIL_MISS/206 33123 GET
> http://www.stf.jus.br/arquivo/biblioteca/NovasAquisicoes/2015-10/1043520/sumario.pdf
> - HIER_DIRECT/201.49.144.135 application/pdf
Lets break this log line down:
At 1457381845.484 (being 1457381845.725 - 0.241) the client
(10.101.1.23) connected to Squid and requested (GET) a Range of bytes
from
http://www.stf.jus.br/arquivo/biblioteca/NovasAquisicoes/2015-10/1043520/sumario.pdf.
Squid found a cache entry claiming to be that resource. But upon loading
it _something_ went wrong (SWAPFAIL) - possibly disk corruption,
possibly I/O error, possibly a different object was found.
Whatever happened, Squid was unable to continue with the cached content
and instead used DNS (DIRECT) to find the origin server.
Squid then contacted the origin (201.49.144.135) and requested
_something_. Received the servers reply and delivered the Range reply to
the client (206).
All of this took 241 milliseconds, and 33123 bytes were transferred to
the client.
Note that there is noting logged about what was requested of the origin
server (no indication whether it was a Range or something else), and no
info about whether the origin produced a small 206 reply, or a
multi-MB/GB full-sized file which Squid would then have to prune down to
the small 3KB Range the client wanted.
Amos
More information about the squid-users
mailing list