On 16/12/2011 6:26 a.m., Elvar wrote:
On 12/14/2011 11:55 PM, Amos Jeffries wrote:
Possibly. You need to track down which of those (DNS lag or HTTP
features) is the cause and find some way to eliminate it. On the DNS
side that means usually having a shared resolver between Squid and
the clients (first lookup will cache the DNS results locally for a
faster repeat). On the HTTP feature side that usually means upgrading
Squid and maybe tweaking the browser config up/down to whatever HTTP
level matches the proxy.
Amos
I set up monitoring for many of the stats pulled from 'squidclient
mgr:info' and I'm wondering what is considered healthy for the dns
response times?
It does depend on where you are in the world in relation to your clients
favorite websites. But I usually looks for <100ms response times. For
lookups in interception where the client has already just done the DNS
request and esentially "primed" the DNS resolver <10ms is expected.
Amos
