Last post Sep 03, 2008 09:09 PM by mydreams
Sep 02, 2008 12:39 PM|rgoyal76|LINK
Hi,I am getting problem with my website after deploying on webserver. When I hits the site first time it takes more then 45/60 sec to load, after that it works fine even I hit it again after closing the previous instance. But if I hit the site agian after
long time (means after a day or 4-5 hours) again it take more time (more then 45 sec) to load.
Size of Home page is normal (200 kb) including images. I am using Ajax which also downloads some script files, Including Ajax files total size is approx. around 600kb.
Is the total size of home page is too big to download or some other reason may possible for the slow performance. How can I check this issue, why it is taking long time to load in first hit.
I uploaded it after publish (precompliled).
Please let me know how can i improve its performance??
Sep 02, 2008 05:20 PM|Bruce L|LINK
ASP.NET compiles the whole application on first load. 45 - 60 seconds is a little bit too much.
Do you have a lot of pages and dlls in your application?
Sep 02, 2008 09:27 PM|rgoyal76|LINK
I have around 20 pages in my site and I am using Ajax Extension and Ajax Control Tool Kit.
Fisrt load means first hit to the site.. after then (after compile) it should work properly. When I hit it next day it takes again long time to load.
Sep 03, 2008 07:17 AM|chenthil_it|LINK
Sep 03, 2008 08:09 AM|rgoyal76|LINK
I have already checked the Viewstate and publishing it with debug="false" mode. I am using VS2008 and .net 2.0. I was getting the same problem in VS2005 also. From where I can set the release mode in VS2008.?
Sep 03, 2008 08:17 AM|TATWORTH|LINK
One thing you an try is to call the site say every 15 minutes e.g. a screenscrape on the home page from a windows service. This will ensure that the site does not time out. It could be that is just lack of memory on the server that is causing the site to
be unloaded from memory.
I have used such a technique on a web service to ensure a rapid response at any time of day.
Sep 03, 2008 11:37 AM|chenthil_it|LINK
The problem is not with performance... It is the intial loading of your application... the worker process and the .net framework will load when you first hit the application and again it deloads when it is inert... Go to IIS and the properties --> asp.net
tab and there are setting do configure it according to your requirements like it should not deloads if it is inert like that.
Sep 03, 2008 11:45 AM|shados|LINK
The option he's looking for is actually located in the Application Pool... I'm not sure how to access it in a development IIS install, but on a Windows Server, you'd right click the app pool, go in its properties, and in the Performance tab, disable the
Idle Timeout property...
I'm not sure if its possible on a development IIS, though. I can't find it in XP, not sure about Vista/IIS7.0
Sep 03, 2008 12:09 PM|chenthil_it|LINK
shados is perfectly right. Check which application pool is the website using and do what shados mentioned.
Sep 03, 2008 09:09 PM|mydreams|LINK
You may use catch(buffer memory) to improve the performance.