On 07/05/2018 12:49 PM, Vishali Somaskanthan wrote: > PFA - pcap and cachelog. Comments appreciated. > Curl timings: > /lookup: 0.062/ > /connect: 0.062/ > /appconnect: 0.081/ > /pretransfer: 0.081/ > /redirect: 0.000/ > /starttransfer: 35.193/ > /total: 35.245/ As far as connection reuse is concerned, the log may show what you have been describing earlier -- Squid opens and abandons S2. Unfortunately I cannot quickly tell what is going on there because it is not an ALL,9 log, but I still suspect there is a bug somewhere. As far as delays are concerned, I see at least one pause or gap in your cache.log, but because it is not an ALL,9 log, I cannot quickly tell what was going on around that gap. It could be that Squid was just waiting for the second request. > 2018/07/03 14:57:40.191 kid1| 33,5| AsyncCallQueue.cc(57) fireNext: leaving Server::doClientRead(local=157.240.22.39:443 remote=10.239.141.26:44707 FD 11 flags=33, data=0x55a01eb64578) > 2018/07/03 14:58:15.175 kid1| 83,3| client_side_request.cc(1721) doCallouts: Doing calloutContext->clientAccessCheck() Others may be able to extract more details from your log. I am pretty sure it is possible. I just do not have the time to do it. Sorry. Alex. > On Tue, Jul 3, 2018 at 9:28 PM, Alex Rousskov wrote: > > On 07/03/2018 06:50 PM, Vishali Somaskanthan wrote: > > Is there any default wait time by squid at any circumstance for getting > > the response from server?? > > No, Squid does not delay regular request processing (unless you tell it > to do that via, for example, delay pools). Many external actors like > DNS, origin server, network, adaptation services, and helpers can > introduce delays, of course. > > Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
