Jore
Member
Hello!
An asp.net site I have developed is dramatically slower when accessed over the internet compared to loading it from the localhost. Here is the deal:
Ive made an asp.net site that has been moved to production now.
When I developed the site I had it both on the local computer where I did the developing and on an intranet server. The loading times of the site were normal from both locations. I only accessed the site from inside the local lan.
Now the production environment is within a customers network and the site has dramatically slowed down. But this only seems to bother when used via internet. When I use the browser over ther at the server (localhost), it works fine. As an example a page that has a calendar control and a datagrid and some other controls as well loads in about one second. But via internet it can take as long as two minutes (which causes the page to timeout).
There is only a 10 Mb network adapter at the server, but when I look at the windows taskmanager networking tab it never utilizes more than 50% of the interfaces bandwidth.
Can there be something in the asp.net that causes it to handle requests from the internet much slower than from ie. localhost?
Of course Internet is always somewhat slower than using a site from the localhost or lan, but not that much.
I saved the slow page that I mentioned earlier and the saved it as an html-page with images and all but which does no queries or other functionality (just a saved copy of the source). I put it inside virtual directory where the site is and tried to load that over the internet and it loaded fast (normally). So to me it really looks that asp.net has some issues on multiple users or serving the pages to internet requests or something..?
An asp.net site I have developed is dramatically slower when accessed over the internet compared to loading it from the localhost. Here is the deal:
Ive made an asp.net site that has been moved to production now.
When I developed the site I had it both on the local computer where I did the developing and on an intranet server. The loading times of the site were normal from both locations. I only accessed the site from inside the local lan.
Now the production environment is within a customers network and the site has dramatically slowed down. But this only seems to bother when used via internet. When I use the browser over ther at the server (localhost), it works fine. As an example a page that has a calendar control and a datagrid and some other controls as well loads in about one second. But via internet it can take as long as two minutes (which causes the page to timeout).
There is only a 10 Mb network adapter at the server, but when I look at the windows taskmanager networking tab it never utilizes more than 50% of the interfaces bandwidth.
Can there be something in the asp.net that causes it to handle requests from the internet much slower than from ie. localhost?
Of course Internet is always somewhat slower than using a site from the localhost or lan, but not that much.
I saved the slow page that I mentioned earlier and the saved it as an html-page with images and all but which does no queries or other functionality (just a saved copy of the source). I put it inside virtual directory where the site is and tried to load that over the internet and it loaded fast (normally). So to me it really looks that asp.net has some issues on multiple users or serving the pages to internet requests or something..?
Last edited by a moderator: