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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Increase DNN load-time on busy sites with windows firewallIncrease DNN load-time on busy sites with windows firewall
Previous
 
Next
New Post
7/29/2006 10:56 AM
 

first, you're looking at the root effect and not causes. if it was the size of your installation, then turning off IIS Requests during the recycle phase wouldn't help either, your site would simply not restart.  So that in itself cannot be a root cause.

The fact that you say that cpu never really reaches any peak (and I'm assuming any one processor is not reaching peak there) also dictates that the system is not busy processing during this phase.

Thus, it's deadlocking - somewhere.  otherwise, it would start up.  When you get right down to it, if the CPU isn't slammed, it's in a wait queue.  There's no magic there.  What's it waiting for is the real question - threads? deadlocking somewhere inside of appstart? locked on a file system file?  etc,etc - but there's very few things that stop execution of code.

Do some engineering analysis.  force recycles by touching your web.config and monitor what happens, that should give you a better clue.  an example:  two windows, one sit on the sql trace start button, the other, readying to save the web.config.  hit them both at the same time.  what happens in sql trace?  what's the last thing that gets executed before it sits - or is it continually retrying a procedure?  again, that should leave you to a second part which should help you narrow down the focus of your investigation.

Or it simply could be that .NET / DNN can't handle that many incoming requests during a restart - in which case, split up your installation - however, I doubt very much that is the cause, but more likely something happening during app start in dnn, that just doesn't predict that so many incoming requests will occur at the same time as the app start sections are being handled.  Which is why I suggested try removing sections from the httpmodules section and see the affect, but you're going to have to do something - no one's going to give you an answer to this without you narrowing down the scope.  That being said, if you don't want to do it - then simply turn off IIS during the restarts and get around it that way.  Choice is yours.

 

 
New Post
7/31/2006 3:03 PM
 
A big, big thanks goes out to John Mitchell who helped me with this.  The net result is that, prior, DNN took (I timed it!) approx. 22 minutes to load 1/4 of the time, and never loaded the other 3/4 of the time.

Now, after some help from John with IIS scripting, DNN takes 52 seconds to load at the most!

Thanks JohnM!!!!

Next on the list:  Find out why DNN crashes :)
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Increase DNN load-time on busy sites with windows firewallIncrease DNN load-time on busy sites with windows firewall


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