My support person, on my hosting site, explained this is why the slow load(see below).  The problem is I am not sure how to do what they are telling me to so.  I know where the scheduler is  it is how to create or call a task that "your sites is being browsed ", setting the frequency it calls the task seemed simple enough.  Also I am assume this schedule runs without the application actually being initiated is that correct? Like a webservice?



To optimize system resource for other clients in the shared hosting server, we will recycle the application pool when it is idle for 20 minutes. If the application pool in which your DNN is recycled, your DNN had to be recompiled before it is available and hence it take a respectively longer time to load.

In order to help you regarding this issue, you can create a scheduled task in which your sites is being browsed at an internal of, let say, 15 min to reduce the number of application pool recycling. You can create scheduled task using control panel. Then click on "Site Admin" and then "Scheduled task" under "Others".

I will second the recommendation of www.host-tracker.com I use them for my sites and it works perfectly.

I have noticed better performance having it hit the default.aspx page rather than the keepalive.aspx page...I am not sure why but it works.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

I have read much on this Forum regarding KeepAlive code running in the webserver which periodically issues a series of HTTP GET web requests to keep web resources alive. From the postings it would appear that one common technique is to trap a HTTP module Dispose method to drive such KeepAlive functions. Unfortunately, by the time a HTTP module Dispose method is driven, the application is almost completely shutdown.  It works, but it is rather inefficient.

I would offer an alternative technique based on the ASP.NET 2.0 Health Monitoring heartbeat web event. Within Health Monitoring web.config settings, one can set the heartbeat web event at a frequency as desired by the application.

CLICK HERE to download a FREE sample Health Monitoring web event provider (HeartbeatKeepAlive), which intercepts the heartbeat web event and activates KeepAlive functions to keep one or more applications alive. I prefer the heartbeat web event technique because it consistently keeps web applications alive before an application shutdown is already underway. This technique also works well with any ASP.NET 2.0 compliant application; DotNetNuke application or non-DNN applications.

HeartbeatKeepAlive sample code is in the form of a VS.NET 2005 C# project, with a download size of 8mb. You will be prompted to login, at which point click on Register to create a user account, and you will be emailed the FREE sampleproject.  This FREE download is available for 30 days.

Philip