This is because of IIS and the worker process being cycled down if the application does not have any activity.

The reason it is there is to free up the resources, and on hosts with lots and lots of shared resources they will even recycle apps more aggresively to get as many accounts onto one server as possible.

To get around it (and drive your host crazy), subscribe to a monitoring or keep-alive service.

http://www.host-tracker.com has a free one that works great.

You might also try my free PageBlaster . It won't make the startup after a recycle a lot faster, but it can help because your cached pages will be delivered from disk like a straight html page unstead of having to build it again from the DB.

A combination of "keep alive" and dynamic page output caching with http compression is your best bet for a speedy DNN site.

For W2k3 server In the properties for the App Pool there are settings to recycle based on memory usage, after a certain amount of time, and after a certain amout of idle time.

For W2k server you need to change it in the Machine.config file (processModel node).