>>>>The hosting company tech support told me this:
>>>>
>>>>"There is always a startup delay with any ASP.NET site if it does not receive constant traffic.
>>>>
>>>>After 20 minutes of inactivity server unload application domain, any subsequent hit will trigger application reload and ASP.NET JIT compilation which results in 5 to 10 second delay."
>>>
>>>I know that's the line with DNN apps, but it just doesn't happen with my homegrown ASP.NET apps. Perhaps I'm just lucky, but I think the real reason is some bad code in DNN.
>>
>>Here's another interesting point found in here: http://forums.asp.net/thread/1224347.aspx
>>
>>"Your regular ASP.NET 2.0 site DOES need the pinging too. It just needs to compile alot less code th[A]n DNN so it looks like your regular site doesn't need pinging."
>
>Thanks for the link. Reading that thread just confirms that DNN is poorly written.

Well, I didn't get that from that link. DNN is doing a lot more than a hand-made site. MaxFrame is much larger than hand rolled VFP stuff, but the average programmer can't compete with MaxFrame's code.

I'd gladly wait a little since the alternative is to spend 4 days doing an event calendar versus 10 seconds to install DNN's event calendar module.

I know switching the skin made a performance boost before I switched hosters.

I'm going to optimize see what I can do to optimize the site further.

http://www.websiteoptimization.com/services/analyze/