Why are DotNetNuke pages very slow to load some times and not others?
DotNetNuke pages can be slow to load sometimes. Here’s why (and how you can minimize the problem)… DotNetNuke is basically a program that runs when requested by the web server. The web server is “smart” in a sense. If no one is requesting pages from the DotNetNuke program, after a while (typically 5 minutes of inactivity) it stops DotNetNuke, releasing the memory and CPU (processor) so they are available to do other work (e.g. for other web sites hosted on the same server) or to save energy (by going into a “quiet” state). In general, this is a good thing. However, the “penalty” comes when a visitor requests the first page from your idle DotNetNuke site. The web server has to start DotNetNuke and that can take a few seconds. Then DotNetNuke can deliver the page. Usually, this is a small price to pay to keep the server running efficiently. It is important to note that once DotNetNuke is running, all subsequent pages are delivered much more quickly for all users. And the server caches
