[squid-users] HTTP performance hit with Squid
squid3 at treenet.co.nz
Fri Oct 23 04:26:06 UTC 2015
On 23/10/2015 4:21 p.m., SaRaVanAn wrote:
> I tried by disabling internal dns in squid. Still i am seeing the same
> What else can be looked at ? Its really makes user experience bad if he
> tries URL for the first time.
Internal DNS in Suqid has very little to do with this. The DNS helper
process will be even slower.
There are three problems here.
1) the serial DNS lookups done by 3.1. The fix for that is upgrading to
a current Squid where that is no longer done.
2) the 3.1 behaviour of looking up DNS for each server connection
attempt. The fix for that is upgrading to a current Squid where that is
no longer done.
NP: this is not helped by your "server_persistent_connections off"
3) the 1 second round-trip delays to the Google DNS servers. I know
there is a lot of avertising about how fast Google services are. But
that really is only advertising, some networks it is not true. Yours
appears to be one of those.
I suggest installing a local bind DNS server on your network and using
that. You may need to redirect client UDP port 53 traffic to it to
prevent them getting the bad behaviour from Google DNS or "Host forgery"
complains from Squid.
PS. dns_v4_first sorts the results found in DNS so IPv4 are connected to
first by TCP even if IPv6 is available and working better. It does not
affect the fact that both A and AAAA are being fetched.
More information about the squid-users