Re: [squid-users] cache_peer configuration is not being reliably hit in Squid 3.2.1

On Thu, Sep 20, 2012 at 9:19 PM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
>
>
> The suspicious thing about this is that client aborts after only 83
> milliseconds. Barely enough time to get DNS data and start the TCP handshake
> to upstream on a MISS. You can expect RTT to be between 50 and 150
> milliseconds to most sites, depending on how far away they are. It looks
> like the outcome of happy-eyeballs algorithm being applied over your proxy
> and some alternative connection succeeded faster at 83ms.
>

Ah, sorry, I may have picked a poor entry from the access.log - I'm
repeating this with curl, and aborting repeatedly. Here are a few
entries from the log that have more realistic timings, and their
associated cache.log times.

     1348118283.864 1368 10.3.100.40 TCP_MISS_ABORTED/200 885030 GET
http://appldnld.apple.com/iOS6/Restore/041-7181.20120919.lEuOK/iPhone4,1_6.0_10A403_Restore.ipsw
- FIRSTUP_PARENT/127.0.0.1 application/octet-stream 1337 127.0.0.1
objectcache-peer 60084 127.0.0.1 51172
http://www.getoffmalawn.com/static/squid/1348118283.864.front.log
http://www.getoffmalawn.com/static/squid/1348118283.864.peer.log

     1348118621.885 1103 10.3.100.40 TCP_MISS_ABORTED/200 1640988
GET http://appldnld.apple.com/iOS6/Restore/041-7181.20120919.lEuOK/iPhone4,1_6.0_10A403_Restore.ipsw
- HIER_DIRECT/150.101.195.90 application/octet-stream 1060
150.101.195.90 appldnld.apple.com 80 10.107.11.155 48122
http://www.getoffmalawn.com/static/squid/1348118621.885.front.log
http://www.getoffmalawn.com/static/squid/1348118621.885.peer.log

Nathan.
Received on Fri Sep 21 2012 - 03:21:58 MDT