On 18/08/2014 11:48 p.m., babajaga wrote:
I have a squid 2.7 setup on openWRT, running on a 400Mhz/64MB embedded
system.
First of all, a bit slow (which is another issue), but one site is
especially slow, when accessed via squid:
1408356096.498 25061 10.255.228.5 TCP_MISS/200 379 GET
http://dc73.s290.meetrics.net/bb-mx/submit? - DIRECT/78.46.90.182 image/gif
1408356103.801 46137 10.255.228.5 TCP_MISS/200 379 GET
http://dc73.s290.meetrics.net/bb-mx/submit? - DIRECT/78.46.90.182 image/gif
Digging deeper, (squid.conf: debug ALL,9) I see this:
2014/08/18 11:17:26| commConnectStart: FD 198, dc44.s290.meetrics.net:80
2014/08/18 11:18:00| fwdConnectDone: FD 198:
'http://dc44.s290.meetrics.net/bb-mx/submit?//oxNGf
which should explain the slowness.
Example of http-headers:
Cache-Control no-cache,no-store,must-revalidate
Content-Length43
Content-Type image/gif
Date Mon, 18 Aug 2014 10:04:52 GMT
Expires Mon, 18 Aug 2014 10:04:51 GMT
Pragmano-cache
Servernginx
X-Cache MISS from my-embedded-proxy
X-Cache-LookupMISS from my-embedded-proxy:3128
---
Acceptimage/png,image/*;q=0.8,*/*;q=0.5
Accept-Encoding gzip, deflate
Accept-Language de,en-US;q=0.7,en;q=0.3
Connectionkeep-alive
Cookieid=721557E9-A0E0-C549-7D6A-B2D622DA4B1F
DNT 1
Host dc73.s290.meetrics.net
Referer http://www.spiegel.de/
User-AgentMozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101
Firefox/31.0
I can only suspect something special regarding their DNS.
Any other idea ?
I agree, its likely their DNS response timeor TCP handshake timeouts
happening.
The latest squid-3.x stable releases may be able to help with this. We
have separated the DNS lookup and TCP handshake operations so the info
about bad connections is stored longer for overall faster transactions.
Also, in my experiene the worst slow domains like this are usually
advertising hosts. So blocking their transactions outright (and quickly)
can boost page load time a huge amount. It is worth having a look at
what those requests are for.
Amos
