Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Troubleshooting DNN Performance Issues?Troubleshooting DNN Performance Issues?
Previous
 
Next
New Post
10/21/2011 3:43 PM
 
Hi,

We have recently been experiencing a lack of performance from our Windows 2003 SP2 server.  It seems that every so often, two problematic DNN sites will both try to compete for CPU resources and thus slow down the entire server.  It's always one or the other or the combination of both at the same time.  We have tried several things to try and narrow down the problem...

-Upgraded the two problematic instances to DNN6 from DNN5
-Performed the optimization techniques/tips from Mitchell Sellers blog on one of the instances to see if it would make a difference
-Before we had this problem, we ran each of our sites in their own App pool.  We read somewhere that minimizing the number of app pools could have an effect so we distributed our sites into only 5 app pools.  Still the two problematic instances continued to misbehave.

What's puzzling is that we have lots of other DNN instances that run wonderfully.  One of them even being on DNN4!  We are led to believe that there is something going on with these two sites specifically.

I've heard of some 3rd party modules being the culprits in some cases.  The modules used in the problematic sites are also used in other instances and do not cause problems.

So how can we narrow this down?  Is there some kind of performance monitor for DNN that can log exactly what is occurring during those heavy workloads?  What else can be looked into? 

Any advice would be appreciated.

Thanks,
Chris
 
New Post
10/21/2011 6:35 PM
 
Hello,
this is always a tricky one. Reducing the number of app pools can help as each app pool consumes ~50mb of ram (each has it's own overhead and a copy of the .net framework), so reducing the number frees up RAM for other sites to use for cache etc.

There are also some good best practices to be found at http://www.dotnetnuke.com/Resources/W...

However in this kind of case theres often 1 item causing the issue - sometimes it gets into a permanent loop (because of particular data) or perhaps the structure of the site causing it to consume too many resources (e.g. a site with 5 portals operates a lot differently than a site with 5000). It's always worth checking the event viewer to see if any issues are logged (http://www.dotnetnuke.com/Resources/W...) and if you're running DotNetNuke 6 or above set log4net to ALL to see if you can glean any interesting data (http://www.dotnetnuke.com/Resources/W...)

The most common issue though is database related, and the best solution for that is to run a sql server profiler trace to see if you can determine the long running event. Finally, on the same note the most common reason we see for the CPU spiking is the existance of a sql deadlock - these are rarely core items as we use a thinly grained approach to database operations, mostly they are 3rd party modules. You can read more on detecting deadlocks at http://www.dotnetnuke.com/Resources/W... (and it''s related links)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
10/24/2011 9:21 AM
 
Thanks for this...

I will look into these.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Troubleshooting DNN Performance Issues?Troubleshooting DNN Performance Issues?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out