Terrible DotNetNuke performance

Question

I\'m involved with a project using DotNetNuke version 05.01.04 Community Edition. We are building our new Intranet using it, but performance is terrible.

Answer 1

I think you need to start investigating this using performance profiling tools. For the DNN application itself I'd grab something like JetBrains DotTrace or Red Gate's ANTS Performance Profiler.

For the database SQL Server Profiler would be the first choice or a tool such as Red Gate's SQL Response.

Without profiling the application these you're going to be pulling at straws.

And as Tim pointed out in his comment, installing Firebug in Firefox with the YSlow add-in to see what resources are taking longest to serve to the browser.

Answer 2

Have you considered creating this lot of pages directly through TSQL? It's not hard to do and may save you a lot of time.

Answer 3

I have several years of dnn development and maintainance experience, when I have this kind of problem, I start doing things from database clean up. Next thing is, find for missing indexes, and/or rebuild all the indexes periodically (sql job scheduled for that) but major performance gain would be from clean up of table

Another good considerations would be, disabling trace, debug mode to false and turn off features of dnn that you don't use (scheduler is the first one to turn off)

Edit: consider keep alive as well Hope this helps

Answer 4

Mitchel Sellers has some good tutorials and checklists to go through with regards to performance in DNN. Start with Explaining High Performance DotNetNuke Configuration and Management (which points to some of his earlier articles).

Answer 5

Is your database on that server? If so, just throw in some more RAM, or get a faster disk array...