RE: [squid-users] TCP_MISS on every attempt

> I've been trying to understand why it's soo slow (45 seconds
> to load www.cnn.com on an empty T1) so I've been looking at
> the logs again. Some pages fire right up, others take ages.
>
> 1046889154.262 11386 66.153.36.134 TCP_MISS/200 47755 GET
> http://www.cnn.com/TECH/ - DIRECT/64.236.24.12 text/html
> 1046889220.583 526 66.153.36.133 TCP_MISS/200 47755 GET
http://www.cnn.com/TECH/ -
> DIRECT/64.236.24.4 text/html

Looks suspiciously like an issue with the CNN server farm rather than a
squid issue, judging by the speed of the second request (the above shows
it took 11 seconds the first time and 500 milliseconds the second time)
which has gone to a different address. The two requests are also from
different clients which may or may not have bearing on the issue.

Perhaps you should run a controlled test repeating the request from a
single client with its browser cache set to 0 and stopping and
restarting the browser between each request. You may need to do many
requests to see what is happening at their end.

Michael Lightfoot
Unix Consultant
ISG Host Systems
Comcare
+61 2 62750680
Apologies for the rubbish that follows...
------------------------------------------------------------------------
NOTICE: This e-mail message and attachments may contain confidential
information. If you are not the intended recipient you should not use or
disclose any information in the message or attachments. If received in
error, please notify the sender by return email immediately. Comcare
does not waive any confidentiality or privilege.
Received on Wed Mar 05 2003 - 23:10:11 MST