I have a idea to improve DNN's performance...(Actually, this is not improve, just looks like improve....)

I think DNN should have a mechanism to make itself alive. Because IIS will recyle system resource if the site is not active for a while and this will cause most DNN site has bad initial performance. If DNN has a mechanism to keep itself alive(Including SQL connection), I think this would improve users feeling about the performance a lot.

For how to experience what the users feeling. Just install a DNN and do not connect to it. After several hours, connect to it. In current case, it will cost about 1 mins+ to see the home page.

Thanks, got it..

Does this file run automatically, or I need to call it by my self? Why I ask this question is because I often met the site I connected need to cost more than 10 seconds if that site are not so many users(less than 10 users per day) in general but less than 3 seconds if I connected it then connected it by another computer right away...

keepalive.aspx does not run automatically, and can not be scheduled. You can use it however to ping your site from an external application. The good thing about pinging keepalive.aspx is that it will now show up in the sitelog of dnn.

Also: you should consider just enlarging the default autorecycle time of the application pool. By default this is 20 minutes, which means that after 20 minutes of non activity in the site the application pool recycles

also.. there is this httpmodule: http://www.snowcovered.com/Snowcovered2/DotNetNuke/Modules/Open-KeepAlive-v20-PASrc/id/4023 which is triggered by the application unload and keeps it alive.... never used, but it might be useful to you

DNN Blog | Twitter: @erikvb | LinkedIn: