Running DotNetNuke?&nbsp; Finding it incredibly slow the first time you load a page?<BR><BR>What happens is ASP.NET unloads the DotNetNuke application after a period of inactivity, and then on the next visit, recompiles the entire site.<BR><BR>Strangely, this leads to terrible performance on a slow site, but good performance on a busy site.<BR><BR>So the solution is to make your site busy.&nbsp; :)&nbsp; Or, at least to convince ASP.NET that your site is busy.<BR><BR>An easy way to do this is to grab wget.exe, and create a batch file that does a "wget http://www.mysite.com" every 5 minutes.&nbsp; This resets the ASP.NET idle counter to keep your site from being unloaded.<BR><BR>You can get a Win32 wget.exe <A href="http://users.ugent.be/~bpuype/wget/">here</A>.<BR><BR>Thu, 01 Sep 2005 19:17:09 GMT