![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
In comp.infosystems.www.authoring.html Geoff Cox wrote: [Firebug] I do see the above for 9 requests but thn there is sometimes a delay of 2 minutes before I can use the page .. it's that bit that I want to check on and Firebug shows nothing even after the 2 minutes ...? There must be some software which would show up what is happening? Will this help, prehaps? http://www.websiteoptimization.com/services/analyze/ |
#12
| |||
| |||
|
|
Geoff Cox wrote: On Fri, 04 Apr 2008 10:17:20 GMT, rf <rf (AT) invalid (DOT) com> wrote: Er. It's actually broken into three, a white bit, a grey bit and a cyan (teal?) bit. From what I can determine the white bit is that particular file waiting for an available connection to the host (as in a TCP/IP socket, assuming the client only has a few to hand). The grey bit is from posting the request to receiving the entire object. The teal bit is where they post the milliseconds. I do see the above for 9 requests but thn there is sometimes a delay of 2 minutes before I can use the page .. it's that bit that I want to check on and Firebug shows nothing even after the 2 minutes ...? There must be some software which would show up what is happening? You don't happen to be using PHP, there, do you? |
#13
| |||
| |||
|
|
["Followup-To:" header set to comp.infosystems.www.authoring.html.] On Fri, 04 Apr 2008 13:04:00 +0100, Geoff Cox wrote: On Fri, 04 Apr 2008 10:17:20 GMT, rf <rf (AT) invalid (DOT) com> wrote: Er. It's actually broken into three, a white bit, a grey bit and a cyan (teal?) bit. From what I can determine the white bit is that particular file waiting for an available connection to the host (as in a TCP/IP socket, assuming the client only has a few to hand). The grey bit is from posting the request to receiving the entire object. The teal bit is where they post the milliseconds. I do see the above for 9 requests but thn there is sometimes a delay of 2 minutes before I can use the page .. it's that bit that I want to check on and Firebug shows nothing even after the 2 minutes ...? There must be some software which would show up what is happening? I think either using YSlow -> Components might give you a hint or you could use something like wireshark (and network sniffer) to see how long things actually take (you'll need to break out everything by hand. |
#14
| |||
| |||
|
|
On Fri, 04 Apr 2008 10:17:20 GMT, rf <rf (AT) invalid (DOT) com> wrote: Er. It's actually broken into three, a white bit, a grey bit and a cyan (teal?) bit. From what I can determine the white bit is that particular file waiting for an available connection to the host (as in a TCP/IP socket, assuming the client only has a few to hand). The grey bit is from posting the request to receiving the entire object. The teal bit is where they post the milliseconds. I do see the above for 9 requests but thn there is sometimes a delay of 2 minutes before I can use the page .. it's that bit that I want to check on and Firebug shows nothing even after the 2 minutes ...? There must be some software which would show up what is happening? Cheers Geoff |
#15
| |||
| |||
|
|
On Fri, 04 Apr 2008 10:17:20 GMT, rf <rf (AT) invalid (DOT) com> wrote: Er. It's actually broken into three, a white bit, a grey bit and a cyan (teal?) bit. From what I can determine the white bit is that particular file waiting for an available connection to the host (as in a TCP/IP socket, assuming the client only has a few to hand). The grey bit is from posting the request to receiving the entire object. The teal bit is where they post the milliseconds. I do see the above for 9 requests but thn there is sometimes a delay of 2 minutes before I can use the page .. it's that bit that I want to check on and Firebug shows nothing even after the 2 minutes ...? There must be some software which would show up what is happening? Cheers Geoff |
#16
| |||
| |||
|
|
On Fri, 04 Apr 2008 08:19:50 -0800, Blinky the Shark <no.spam (AT) box (DOT) invalid wrote: Geoff Cox wrote: On Fri, 04 Apr 2008 10:17:20 GMT, rf <rf (AT) invalid (DOT) com> wrote: Er. It's actually broken into three, a white bit, a grey bit and a cyan (teal?) bit. From what I can determine the white bit is that particular file waiting for an available connection to the host (as in a TCP/IP socket, assuming the client only has a few to hand). The grey bit is from posting the request to receiving the entire object. The teal bit is where they post the milliseconds. I do see the above for 9 requests but thn there is sometimes a delay of 2 minutes before I can use the page .. it's that bit that I want to check on and Firebug shows nothing even after the 2 minutes ...? There must be some software which would show up what is happening? You don't happen to be using PHP, there, do you? Yes - in order to access MySQL ... Why do you ask? |

#17
| |||
| |||
|
|
Have you been using Netscape and now feel abandoned by AOL? |

|
Then use SeaMonkey. Go to <http://www.seamonkey-project.org/>. |
#18
| |||
| |||
|
|
You don't happen to be using PHP, there, do you? Yes - in order to access MySQL ... Why do you ask? Because of your issue and something that happened to me about a year ago. It's not a short story. Grab a beer. ![]() Every page at the two sites in my sig require PHP. The top few elements (which I'll loosely call the headers) and all of the footer stuff you will see repeated on every page are PHP inclusions. One day, with my last host, it started taking about four minutes do download a blinkynet page. Any page. And if you go there, you'll see that because I'm on dialup I'm very careful to not make large pages. Those should probably average 10 or 12 seconds on a dialup. So four minutes was just crazy. *I had changed _nothing_ from my end.* And I noticed that this was happening: it would take a minute and a half or two minutes for those PHP-delivered elements to render; then the body of the page would load in a snap, just like the whole page did before this started happening; then it would take another minute or two for those *bottom* PHP-delivered elements to show up. I stress: nothing at all changed from my end. Somehow, PHP was just plain falling on its ass. Remember, the non-PHP bodies of the pages all downloaded in an instant or two while the PHP-dependent stuff (still not many bytes, mind you) just went chugga-chugga for minutes at a time. Of course I couldn't get it through the thick head of that host that I had changed nothing. So I had to leave. I moved the same code to a new host and it worked fine from the git-go, and has ever since. Well, once - long after I moved - I checked blinkynet and found no PHP happening. I did live chat with them when I saw that; within a minute - literally - they said "Try it now", and it was working that fast. They'd accidentally disabled PHP in some fashion. NO problem: they admitted it and, like I said, they kicked the right corner of their hardware to have it functional in the wink of an eye. So that's why I thought if PHP when you described your issues. I'm not using any databases at any of my sites, so I'll grant that there are more things to go wrong with your installation than mine. But your problem sounded very, very familiar. My experience was also a good lesson in how much difference a responsive host can make. |
#19
| |||
| |||
|
|
[Please excuse the blank reply. I accidentally hit the Send button before replying.] |
|
The cross-posting indicates you may have some JavaScript in the pages. Is it possible that the page with the two-minute delay has JavaScript that accesses the Web server for data or for another JavaScript? |
|
I see an excessive delay -- with my browser freezing even for tabs with pages from unrelated servers -- on some pages from Vanguard Mutual Funds. I can avoid the freeze and delay by disabling JavaScript. However, some Vanguard pages then don't work. |
![]() |
| Thread Tools | |
| Display Modes | |
| |