DotNetNuke Optimization

<< Engineer or not Engineer? | Home | WPC 2004... I will be there! >>

DotNetNuke Optimization

In these days I'm working on a personal project with DotNetNuke and I can see that sometimes DNN (2.1.2) is slow at startup, expecially if you have lots of modules loaded.

I've personally tested that the startup performance can be increased by going to the Site Configuration settings and disable the Logging feature (by setting Logging to "0" in Site Settings or Host Settings)... obviously, this could be done if you don't need a logging feature (and I don't need it).

But... are there other way to increase performances on DotNetNuke startup? Ideas?

Print | posted on Monday, September 20, 2004 9:05 AM

Comments on this post

# re: DotNetNuke Optimization

You can set your caching on the modules, go to the module settings and specify a cache timeout. If you have modules that don't need to hit the database every time a page is loaded use the cache. There are also some tips on the Web for manipulating the viewstate within DNN if you want to shorten the download time. Since all pages inherit the base page of DNN, you just need to modify the code within this page.

Left by Patrick Santry on Sep 20, 2004 5:58 AM

# re: DotNetNuke Optimization

Patrick, what could be a good cache value? I've modules with the cache timeout set to 60. If these modules don't need to hit the DB, is it correct or can be incremented?

Left by Stefano Demiliani on Sep 20, 2004 6:22 AM

# re: DotNetNuke Optimization

You can go higher if you want to. Just as with any .NET caching you're going to lose some memory overhead. For items that don't change very often, I use 300 to 600 for the timeout. Also I modify the base page to pull out the viewstate into session state (http://www.wwwcoder.com/main/parentid/224/site/3507/68/default.aspx), but again you incur some memory overhead if you do this, but I would rather have fast loading pages over a slow connection. I can always put more memory into a server, I can't speed up someone's dial-up connection.

I've been running WWWCoder.com on DNN for over a year now, and I just recently upgraded to DNN 2.1.2, I still have to do some customization to the core code to get it do exactly what I want, but it is much less than with DNN 1.x, as DNN 2.1.2 is more flexible with the provider model.

Left by Patrick Santry on Sep 20, 2004 9:18 AM

# re: DotNetNuke Optimization

Interesting Patrick, I'll try to do some modifications. If you have other tips, I'd like to receive them

Left by Stefano Demiliani on Sep 20, 2004 12:30 PM

Your comment:

Title:

Name:

Email: (never displayed)

(will show your gravatar)

Website:

Comment: Allowed tags: blockquote, a, strong, em, p, u, strike, super, sub, code

Please add 5 and 7 and type the answer here:

STEFANO DEMILIANI