Guys=

I'm experiencing an issue with a DNN website.  The users are reporting a long slow load time on the initial load of the site.  The site comes up slow the first time, and then responds ok after that.  I am familiar with how .NET works and that it builds/compiles on the initial load.  But it seems this is happening each time we go to the site.  Maybe this is because there are only a few of us that are currently using the site (at least until it is launched).

I was curious if anyone has any experience with this problem?  Is there a way to control how this works or a way to keep the site active / alive?  Does it have anything to do with DNN caching, or is this a .NET/IIS tweak?

Thanks,
Jones

Hello,

I've experienced this as well as .Net will unload caches after a period of inactivity.  I use a SEO module that has a keep alive feature in it that solves the problem for me (DNNMasters SEO).  There are probably other keep alive modules out there.  I have not seen a default DNN setting for this.

Chuck

The issue here is that, after a period of inactivity, IIS will "unload" your site. The default is (IIRC) 20 minutes. So, you must keep activity going on the site more frequently than every 20 minutes.

If you google "DotNetNuke keep alive" you should find lots of references.

There isn't a default setting in DotNetNuke mainly, I would guess, because this is not an IIS issue. And, it's one that's "fixed" easily.

If you control your IIS (not in a hosting environment) you can change the default setting, too. You could change it to never unload your site.

Thanks guys~  I'm on the right track... thanks to my awesome community of DNNers!