Re: [squid-users] TCP_MEM_HIT long elapsed time

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Thu, 22 Dec 2011 13:10:38 +1300

On 22/12/2011 7:55 a.m., Henrik Nordström wrote:
> ons 2011-12-21 klockan 18:47 +0100 skrev feralert:
>
>> Maybe a dump question: why does it take so long for some TCP_MEM_HITS
>> to 'show up', for example i got this:
>>
>> Dec 21 17:37:15 42721 192.X.X.X TCP_MEM_HIT/200 68873 GET http://example.com
> Possibly ACL processing needing to wait for something (dns lookup, auth
> processing, external acl, ...?)
>
> The time is the time between Squid reading the request and sending the
> last piece of the response.
>
> Regards
> Henrik
>

Could also be a slow client (ie dialup modem). 68KB of data at dial
speeds of 1-2 KB/sec would take that long. Modern browsers open many
concurrent requests, which can drop modem speed down into that range
very easily.

Amos
Received on Thu Dec 22 2011 - 00:10:46 MST

This archive was generated by hypermail 2.2.0 : Sun Dec 25 2011 - 12:00:03 MST