Forum Moderators: open

Message Too Old, No Replies

Slow ASP page output

Windows Server 2003 - ASP page outputs all at once

         

JeannePDA

6:10 pm on Jan 16, 2004 (gmt 0)



I have an ASP page that will not display any of the page until the entire page is done. The page contains a lot of product pictures and descriptions. The page worked fine on a Windows 2000 server, but on a Windows 2003 server you wait for a long time before you see any products (and then you see all of them at once). I have the response.buffer set to false. The page includes a number of nested tables and that seems to be at least part of the problem, as when I tried adding a simple <p>Name of the page</p> at the top of the page that part went ahead and displayed right away. Is this a common problem with Windows Server 2003? How do I work around it?

defanjos

6:20 pm on Jan 16, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Welcome to WebmasterWorld,

Did you check the load time under the two different servers with the same browser version? The reason I ask, is that some browsers take forever to render nested tables (especially Netscape).

This is not the answer to your question, but it is something to consider.

Just an aside, try getting rid of nested tables - they sloooow down pages a lot.

pageoneresults

6:20 pm on Jan 16, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Hello JeannePDA, Welcome to WebmasterWorld!

The page includes a number of nested tables and that seems to be at least part of the problem.

Is your entire page wrapped in an enclosing table? Are all those nested tables inside one all encompassing table for the page? If so, that will cause loading issues as everything inside the enclosing table will need to be read by the browser before rendering.

If the tables are not enclosed in a single encompassing table, then the tables should load from top to bottom or as they are ordered in the html.

If they were working before and not working now after the switch, it sure sounds like a server issue which will probably be answered by one of our Windows server gurus (not me). ;)

f00sion

8:01 pm on Jan 16, 2004 (gmt 0)

10+ Year Member



like pageone said the tables have to be fully read by the browser before they are displayed... if you have a loop generating rows in a table try doing a response.flush every 10 rows or so... you can check if its a server or browser issue by going to the page in question and hitting the stop button before it is all the way loaded, when you view the source you should see the rows outputted in the source just not rendered yet...if there is no output then you've got other issues.