@Leonardo: Thanx a lot. Your logs are much better than mine, although I am
closer to the site.
So I have to look somewhere else, like slow DNS-resolution (I also use
googles 8.8.8.8), or slow conn establishment, as now I have also seen very
long response times durin initial page loads when trying
Didnt noticed any slowness at all when loading www.spiegel.de
through Squid 2.7S9 on a OpenWRT box. I'm using OpenWRT revision r42161,
compiled from scratch. The page fully loaded in about 7-8 seconds. Could
be faster, but i wouldnt call that the 'extremely slowness' you
mentioned. I'm
Sounds good. I also do not like C++ :-)
squid2.7 from openWRT is running on my Open-Mesh; besides the DNS-issues I
have not found any problem. Only a bit slow.
DNS-issues are related to advert-sites only, which is a bit strange. Lokks
like some tricks regarding TTL/DNS-based load sharing, I
Interesting. Have you seen any DNS issues ?
For details, pls ref. here:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Very-slow-site-via-squid-td4667243.html
Or, can your reproduce it here:
www.spiegel.de
--
View this message in context:
@James:
For details of my problems, pls ref. here:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Very-slow-site-via-squid-td4667243.html
Not shure, that it is really squid. Effect is slow loading of objects from
ad-servers.
As I have an open-mesh AP, 64MB RAM, my squid2.7 does memory-only
