I was wondering the same thing. This could have a lot to do with loading the assets and images. It also might make a big difference on browsers. I know that IE usually shows you the layout of the page and loads the graphics within that. Many time I have seen people using netscape and it keeps the screen blank until all images and everything have loaded. You might want to try a simple online tool to test the total download time of the site. I use the one at echoecho.com that checks for HTML validity, load time and some other stuff. The tool's direct link is http://www.echoecho.com/toolhtmlinspector.htm
Hope that helps. John Burns Certified Advanced ColdFusion MX Developer Wyle Laboratories, Inc. | Web Developer -----Original Message----- From: Jim Davis [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 12, 2005 5:10 AM To: CF-Talk Subject: RE: Cold Fusion Page Execution Times > -----Original Message----- > From: Kevin Roche [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 12, 2005 4:17 AM > To: CF-Talk > Subject: Cold Fusion Page Execution Times > > Hi, > > I am investigating the execution times on one of my customer's web site. > > The site uses CF5 and has some complex pages. I was quite happy with > the home page which was excuting in an average of 110 ms. > > However I was still getting some complaints from users about the time > the home page took to respond. You may want to ask them to get specific... what does "respond" mean? Is the page done, but is not navigable (often the case with complex JavaScript navigation)? Is the page done but not displayed yet (can indicate page rendering issues)? > I built a simple tool with CF to measure the time from my desktop > machine using cfhttp. This is a good thing but can't tell you the whole story. I'm sorry if I'm selling you short but I assume the tool is simply fetching the page, right? It's not fetching any of the assets on the page (graphics, style sheets, etc)? Even it were fetching all of them it's not rendering the page like a browser would. The assets on a page can DRAMATICALLY affect rendering time. Images without height and width attributes must be downloading and examined before the page can be rendered. External style sheets must be obtained before anything can be shown and so forth. Even my relatively simple home page (www.depressedpress.com) makes 48 separate requests. www.cnet.com makes (as of right this instant) 148 requests (but still that pages on takes 3.49 seconds to download all its assets over my connection). Lastly such a test would probably be on a more reliable network than the people that have complained. In other words this might give you an idea of page download time but only over your connection. It won't include any of the browser shenanigans or other network issues. > This showed that the average time for the page to return was more like > 1349 > ms. > > I saved a copy of the home page on the server and called it index.htm > so that it was delivered without any interaction from CF5. Now that > page comes back in 556 ms. > > What is causing the big time difference? In this case it's cutting CF from the picture. But the declared "time" for a page in CF isn't the whole story. CF can only start timing a page when it starts working on the page and it stops when it's almost done. The time CF shows doesn't include any of the time the web server might be consuming or and time spent in the CF queue. > If the page takes 110ms to build and IIS takes 556ms to send it I was > expecting a total of 666ms! You might get that sometimes... these are all just point-in-time tests. You might try automating the testing such that you can run it hundreds of times a day and average the results. That would give you a better picture. You could also, for a while, set the "log slow pages" admin setting to 1 second - you'll then see if the home page is ever actually taking longer than you think it should. A tool like HTTPWatch is amazing useful in these scenarios. Although it's not cheap and it only runs in IE it provides a stunning amount of information about the request process. It will log information about the whole page - all the (probably very many) requests that make it up and how they're being cached, found and dealt with. I'd be happy to run it for you and send you the results if you give me the URL to check. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:220802 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
