I'm new to DNN and have built a basic portal. Works great however the first time I load the portal up in my browser it can take anywhere up to a minute to load. However, once I ahve loaded it once and then go to a different computer (with clear cache) and try load it, it pops right up immediatly.

Subsequent loads on all machines are perfect.

Then give in an hour or two and go back to it and there is that HUGE lag time, the first time I access it.

I've actually also noticed this on some other remote DNN sites on the internet. Is it compiling or building the cache or something ? It's very annoying and a real problem.

Thanks

make sure to remove any installed modules you are not using, especially large ones like store, blog and forums.

Precompilation is currently not supported, it is on the core teams radar for a future version (past 5.0).

Why is it killing you?  If it's just a lag for the first request, then don't worry about it.  If it's a lag for EVERY request, then you have a problem.

If you do what I recommend and just get the app pool to recycle ONCE per day at 0-dark-thirty (sometime early morning), you should be fine.  you could even fine-tune this by automating a page request two minutes after the recycle to make sure that the application is precompiled before it gets hit by any humans.

You should, with the proper hardware, be able to install hundereds of Portals per DNN installation.  I'd recommend not installing multiple DNN instances per server, as then you will experience canibalism as the DNN instances compete for resources.