RE: [squid-users] A single website is loading slow

I have had a quick look at the url you mentioned using Squid 3.0STABLE19 and
IE7 (Windows XP SP2).

There are 2 requests in the Squid access log which seem to take a while to
retrieve:
www.realestate.com/css/global/site.css followed by
www.realestate.com/JS/common/re-all/re-all.js. These requests are approx.
200KB and 740KB respectively and take about 24sec and 42sec respectively to
load on our ADSL2+ connection.

When accessing the site directly rather than via squid from the same client,
it takes about 15-20sec for the page to load.

On the second access using Squid, the page loads in approx. 15-20sec.
TCP_HIT is recorded in the Squid access log for the 2 urls mentioned above.

I am not sure why it takes longer to load in Squid the first time except that
maybe it is related to the browser using HTTP1.1 features (Accept-Encoding,
Transfer-Encoding, etc) as I notice the data is compressed for the direct
connection and uncompressed for the squid connection and the amount of data
for the requests is approx 1/4-1/3 for the direct connection versus via
squid. Perhaps Amos will have some ideas?

Regards

Paul

> -----Original Message-----
> From: RM [mailto:bearmeat_at_gmail.com]
> Sent: Wednesday, 8 September 2010 1:29 PM
> To: Amos Jeffries
> Cc: squid-users_at_squid-cache.org
> Subject: Re: [squid-users] A single website is loading slow
>
> On Tue, Sep 7, 2010 at 8:21 PM, Amos Jeffries <squid3_at_treenet.co.nz>
> wrote:
> > On Tue, 7 Sep 2010 19:31:45 -0700, RM <bearmeat_at_gmail.com> wrote:
> >> I am having issues with just a single website loading very very
> slowly
> >> through Squid. The problematic website loads fine without a proxy
> but
> >> takes several minutes to load through Squid. All other websites load
> >> perfectly fine.  I have tried the following:
> >>
> >> 1) I originally thought the issue was DNS related so I changed the
> >> nameservers that Squid uses by using "dns_nameservers". I tried
> >> several different local nameservers and then eventually tried free
> >> services such as Google's and OpenDNS's. No luck.
> >>
> >> 2) To further convince myself it was not DNS, I entered the
> website's
> >> IP/host information into /etc/hosts and used Squid's "hosts_file"
> >> directive to use /etc/hosts. This did not help either.
> >>
> >> Squid was restarted each time after making the above changes.
> >>
> >> Here are the access.log entries related to loading the website (URL
> >> and IP addresses have been changed).
> >>
> >> 1283907376.404    320   222.222.222.222 TCP_MISS/301 508 GET
> >> http://website.com username DIRECT/111.111.111.111 text/html
> >> 1283907415.924  39277   222.222.222.222 TCP_MISS/200 62371 GET
> >> http://www.website.com/ username DIRECT/111.111.111 text/html
> >>
> >> As you can see, the first log entry appears quickly after attempting
> >> to load the website. The title of the website appears in the web
> >> browser's title bar almost immediately but the content of the
> website
> >> does not load until much later.
> >>
> >> Any help is much appreciated.
> >
> > You have erased the vital information about *which* website URL and
> > *where* it is. Have not provided any information about which squid
> version
> > you are talking about either.
> >
> > To get any type of useful help you need to present enough facts for
> > someone else to replicate the problem please.
> >
> > All we can do at this point is say "yes. Your log shows that a
> website is
> > loading slowly". Other sites work fine? then conclude that the
> problems is
> > not in Squid itself but somewhere else which impacts Squid.
> >
> > Amos
> >
>
> The website is www.realestate.com
>
> I am using Squid Cache: Version 2.6.STABLE21 on CentOS 5.5 32-bit
>
> Thanks.
>
>
> __________ Information from ESET Smart Security, version of virus
> signature database 5432 (20100907) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
 

__________ Information from ESET Smart Security, version of virus signature
database 5432 (20100907) __________

The message was checked by ESET Smart Security.

http://www.eset.com
 
Received on Wed Sep 08 2010 - 05:54:59 MDT