Hi,
Just want to put my two pennies in. 'Slow' internet navigation through
squid is often observed in case of incorrect DNS server settings on
squid box. Often issues are:
- ipv6 DNS queries are performed first;
- first DNS server in /etc/resolv.conf is not responsible.
Both of these cases give plus 5-7 seconds to each request (dns request
time-out). So I'd recommend to make sure that DNS is not an issue here.
The easiest way to find out the place where delay is added is to sniff
request-response on squid box. Capture will show you what part of the
path adds delay.
Best wishes,
Pavel
On 11/25/2013 03:57 PM, Kinkie wrote:
On Mon, Nov 25, 2013 at 11:26 AM, Michele Mase' <michele.mase@xxxxxxxxx> wrote:
Problem: internet navigation is extremely slow.
I've used squid from 1999 with no problems at all; during last month,
one proxy gave me a lot of troubles.
First we upgraded the system, from RHEL5.x - squid 2.6.x to RHEL6.x
squid3.4.x with no improvements.
Second, we have bypassed the Trend Micro Interscan proxy (the parent
proxy) without success.
Third: I do not know what to do.
So what should be done?
Some configuration improvements (sysctl/squid)?
Could it be a network related problem? (bandwidth/delay/MTU/other)?
Hi Michele,
"extremely slow" is quite a poor indication, unfortunately. Can you
measure it? e.g. by using apachebench (ab) or squidclient to measure
the time download a large file and a small file through the proxy from
a local source and from a remote source. Then repeating the same from
the box where Squid runs and then from a different box.
Think about what has remained unchanged since when there was no
performance problems: e.g. network cables, switches, routers etc.
Kinkie
