I'm developing a website for my "other" business that is using ASP.NET.
Everytime I go to the site after about 30 minutes or so, the page takes 30-40 seconds to load which is unacceptable. Anyway, If I let this page load completely and then go back to the age 10-15 minutes later, it comes right up (even if I clear my local browsers cache). If I wait more than 30 minutes or longer the same 30-40 second delay is noted for the first load and then it loads fine again.
I assume the app is recompiling itself? I am making no changes to the code between these hits.
I heard somewhere that there is a built-in timeout of 15 minutes for the compiled version in ASP.NET so if there are no hits in 15 minutes, the app auto-recompiles itself; is this true? And if so, how can I avoid this? My prospective customers are turning away before the page fully loads. Any help would be GREATLY appreciated!!
BTW, the site is: (watch the huge delay for loading the first time)
Thanks,
Steve
Everytime I go to the site after about 30 minutes or so, the page takes 30-40 seconds to load which is unacceptable. Anyway, If I let this page load completely and then go back to the age 10-15 minutes later, it comes right up (even if I clear my local browsers cache). If I wait more than 30 minutes or longer the same 30-40 second delay is noted for the first load and then it loads fine again.
I assume the app is recompiling itself? I am making no changes to the code between these hits.
I heard somewhere that there is a built-in timeout of 15 minutes for the compiled version in ASP.NET so if there are no hits in 15 minutes, the app auto-recompiles itself; is this true? And if so, how can I avoid this? My prospective customers are turning away before the page fully loads. Any help would be GREATLY appreciated!!
BTW, the site is: (watch the huge delay for loading the first time)
Thanks,
Steve