Last post Jul 16, 2008 06:28 PM by Dimacorp
Jul 16, 2008 09:59 AM|Dimacorp|LINK
I am trying to find out what causes excessive load time of the ASPX page? This happens only on particular customer server. I have a simple, Hello World page, no connection to the database. The page takes
more than a minute to load, initially. After it loads once, next time it loads very fast. Then if you wait some time, an hour or so, it loads very slow again. We pre-compiled the application but it makes no difference.
How can I check what services should be running (always) on the web server? Is it possible that a certain .NET service does not run and only starts when a page is loading? What should I monitor on the server when loading a page?
Thank you in advance for any suggestions.
Jul 16, 2008 10:01 AM|MelvynHarbour|LINK
Turn on trace and watch what happens. That way you'll be able to see whether it's part of your code or something external.
Jul 16, 2008 10:25 AM|anup_daware|LINK
There are two things to check
Above terms may sound taste-less but are very important.
According to me it is very important to know which of these is causing the real problem.
Sometimes out backend is very fast but UI takes more time to load so images or CSS etc
I suggest you to use following tools:
1. For UI: Firebug extension of firefox along with Yahoo Performance parameters YSlow
Firebug will show you the size of files (images, JS, CSS etc), check if some particular file is causing the problem, set the file as static content in IIS
2. For Backend: Use VSTS profiler, this is a great tool, which can tell you which of your function is taking more time
Alternately you can also use, Environment.TickCount to measure the performance
Let know if you need more info.
Jul 16, 2008 10:32 AM|Dimacorp|LINK
It has to be something external. The only code I have on my page is a simple text "Hello World". So, I just can't see how the Trace will show me anything. Has to be something to do with the way .NET 2.0 is setup on the server.
Thank you for your suggestion.
Jul 16, 2008 10:33 AM|Dimacorp|LINK
The simple page has no images, no connection to the data, nothing but the text "Hello World"
Thank you for your suggesiton.
Jul 16, 2008 01:28 PMemail@example.com|LINK
After it loads once, next time it loads very fast. Then if you wait some time, an hour or so, it loads very slow again.
ASP.NET caching, plus some JIT compiling. As long as the page is requested at least once every twenty minutes, it stays in cache. So get more visitors.
Jul 16, 2008 06:28 PM|Dimacorp|LINK
I found the solution to the problem.
The issue was that the Application Pool Idle timeout was set to 20 minutes. Therefore, if nobody was using the application, IIS was shutting down the worker processes after being idle for 20 minutes.
I created a separate Application pool for my application and set the Shutdown setting to 2000 minutes.
Thank you all for your input.