Geek Answers Handbook

The awful performance of DotNetNuke

I am participating in a project using DotNetNuke version 05.01.04 Community Edition . We are building our new Intranet using it, but the performance is terrible.

We have five people adding pages and content to it, and every 15-30 seconds they pause for 10 seconds or longer before the system continues to work and the following screens load.

Windows 2003 server, 3.8 GHz with 1 GB of RAM. I told the server administrator that processor and memory performance is not a bottleneck.

Currently, we have 350 pages in the system, we plan to add 1000. Therefore, we need to solve this performance problem so that we can enter content, and therefore we can live life.

I just don’t see where the bottleneck is. Is there a good reason to spot a bottleneck when using DotNetNuke?

Installed Modules

  • Publish: Participate (Not currently in use)
  • Blaster page (does not appear to provide caching when users login authentication)
  • Simplegallery
  • Xmod
  • Content manager

Configuring IIS
Recycling applications is completely disabled (except for 2 or more)

New results: March 18, 2010. The
main bottleneck was the appearance of version 5.1.4 with an error that caused 1300 database calls on the middle page due to broken database caching in memory. We upgraded to 5.2.4, which resolved this bottleneck.

. DDR: DDN: Nav, .

, ?

+5
5

, , . DNN - JetBrains DotTrace Red Gate ANTI Performance Profiler.

SQL Server Profiler , Red Gate SQL Response.

.

, Firebug Firefox YSlow, , , .

+5

Mitchel Sellers , DNN. DotNetNuke ( ).

+4

, , - , - / ( sql),

: , false dnn, ( )

: ,

+3

? , ...

0

Have you considered creating this batch of pages directly through TSQL? This is not difficult to do and can save you a lot of time.

0
source

More articles:


All Articles