Hi,

I have an ASP based application which is using SQLServer 7.0 database. The problem i am facing now is:

When i access the ASP pages from the browser, WITH PROXY, it is very fast.
When i access the ASP pages from the browser, WITHOUT PROXY, it is unreasonably slow.

And about my environment:
-------------------------
The database i am using is a clustered SQLServer 7.0 and it is high end infra.
The web server i am using is win 2003 server based. More importantly, the webserver was recently upgraded from its earlier Win NT 4.0 Server to Windows 2003 server.
Database does not contain huge data since we have just deployed the application.
The page i am accessing does not contain too much graphics.
I am using the pragma, no-cache directive to force the browser to fetch the page directly from the server(instead of proxy).

With the above things, i do not know why the pages are very slow. And why the pages are very fast thru proxy? My pages are basically database linked pages and regardless of the proxy, performance must be the same for both cases - with and without proxy. Even if it is slow, i would expect it to be slow under both circumstances as proxy can not cache the database content. In my case, with proxy, the page access is fast.

I suspect there is some problem with the network settings(how it is routed, gateways, etc...). But i have no proof to say that.

I am still fighting to resolve this. Pls help.

Thanks,
Peria.

This is a tricky one. I think you'll need to narrow down the possible problems via the process of eliminiation

The problem is one of two things:
1. Slow network
2. Slow server

My guess is that that there are network issues and that your page is running fine. What you can do is put code in your page to measure how long it takes the page to process, and output this to the screen. This can be done with a simple script...

At the top of your asp page put

<%
dim elapse
dim start
start = timer
%>

at the bottom of the page put

<%
elap = timer - start
response.write(elapse)
%>

*i didn't actually test this code

if the elapse time is nearly the same with and without the proxy, you'll at least know that it's a network problem, and not a problem with your server. If the elapse times are vastly different you probably have an issue with the servers.

Good luck and please let me know what happens

Hi Doarian,

As i was on leave, i could not respond immediately and am extremely sorry for that.

I will try your suggestion and will get back to you :-)

Thanks a lot.

Regards,
Peria

I am having a very similar issue.

My ASP page loads fast on the Win2k Dev. server, but very slow on Win 2003 Live server.

Live Server (Win 2003): 10.031 seconds to load
http://www.specialopspaintball.com/b...ew.asp?id=1088

Dev. Server (Win2k): 2.14 seconds to load
http://paintball.netcentrixllc.com/b...ew.asp?id=1088


I am going to add that code to help determine if it's the server or network.

Where does the proxy come into this ?

more importantly;
where is each server in relation to the viewing point in the network topography?
Did the upgrade replace the server hardware or just the OS?

<added> Just a quick check on grabbing source (not a browser), and the loading times are not that different.There is a noticeable pause in the data stream. So I would suggest that you look at how the queries are being done and improve the efficiency of those. Also a lot of the speed issues are in the mass of nested tables and rendering. Tables are not rendered to the browser until the last closing </table> tag is streamed out, so the small pause in the data stream will cause a longer delay in display.
</added>