Requesting keepalive.aspx is loading the .Net Framework (through the default HTTP Handler) - but all DNN specific dlls keep still unloaded. That's the reason for the fast reply of keepalive.aspx but a still existing delay on default.aspx. The advantage of using keepalive.aspx is that the requests are not logged by the portal and so your reports are accurate.

My frist tipp: create a dummy page (don't show in the menu) using DNN Admin - Pages Menu. Place all the modules you use on your hompage also on this page and let a professional KeepAlive Service (have a look at www.dnnportal.eu) request this page every 5 minutes.

My second tipp: if you have full access to the IIS you can additionally optimize the Application Pool settings to recycle only at given times (e.g. 2-4 times a day). But never - again: never - disable this memory and proc optimization feature!

Stefan

Stefan,

Could you explain why a "professional KeepAlive Service" would work better than SmarterPing? Also, I like your idea of hitting another 'hidden' page - I guess I could just set LiveStats to ignore that page like I do keepalive.aspx?

Also, I have read in some posts that 'disabling logs' can speed up DNN sites. How do you do that? Does that mean DNN logs or server logs? Would that affect LiveStats results?

Thanks,

Will
www.planetmaine.net