Steven,

The issue isn't unique to DotNetNuke applications, it actually applies to ANY ASP.NET application as it is an IIS configuration item that causes the worker process cycling.  It is a bit more visible on DNN sites at times simply because of the size of DNN.

I personally recommend a 15 minute interval for the keep alives, that will get you a request within the time limit while limiting the wasted bandwidth.

---

-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 also noticed this on two of my sites. One is hosted by webhost4life, and the other is hosted by godaddy. I have SmarterPing for the keepalive program. I have tried changing the ping time from 5 mins, 10 mins, and 15 mins intervals, but none seem to make a difference to keep the site alive.

Can the hosting company configure any settings to have page requests to a certain page ignored?

If it's not working with keepalive.aspx then by all means try it with another page... at least as a test.

It's true however that a site without enough traffic to keep itself alive is not supposed to be loaded. There simply isn't enough ram on most cheap shared hosting accounts to handle 150Mb+ for every DNN portal. Even if there is enough ram for 30 DNN portals (and these shared servers usually have hundreds of sites on them), the disk is going to have a difficult time keeping up. Hosters rely on the majority of sites being idle or unloaded in order to provide these accounts.

In my experience, DNN is just too piggy to share... oink oink!

Rob