[squid-users] Squid-3.5.28 slowdown

Amos Jeffries squid3 at treenet.co.nz
Fri Mar 1 12:21:37 UTC 2019


On 1/03/19 10:47 pm, Michael Hendrie wrote:
> Hi Guys,
> 
> I have a squid-3.5.28 installation that is deployed to do transparent
> ssl-bump of HTTPS traffic (linux bridge, tproxy).  The server is not
> overly busy, CPU and RAM usage is low + no swap being used yet regularly
> the squid service is choking HTTPS traffic to a point where websites are
> timing out.  Any other traffic flowing through the bridge is unaffected
> and continues to operate at normal expected speeds.
> 
> I have checked all obvious things, CPU/RAM usage, network interface
> errors, conntrack table and TCP resource exhaustion yet all look fine.
> There is no caching taking place and disk IO is not a problem.
> 
> During the times where squid is slow, even using squidclient to query
> squid state is extremely slow to respond, as you can see below snip from
> the access.log the mgr:coutners and mgr:5min requests are taking up to
> 30 seconds to complete when usually the response time is 0:
> 
> 1551397216.978     31 127.0.0.1 TCP_MISS/000 0 GET
> cache_object://localhost/5min - HIER_NONE/- - -

If that '31' is what you are meaning by "30 seconds" then please be
aware the duration column numbers are in *milli*-seconds.

So while in absolute terms this 31ms is significantly slower than
under-1ms (aka '0'). It is not humanly visible.

Any visible delays you may be having are not being shown by these log
entries. Which hints that they are somewhere in the delays between HTTP
transactions - either the I/O on traffic not yet logged, or in the TLS
handshake timings.

Amos


More information about the squid-users mailing list