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/22/2006 4:11 PM
 
Hello,

I've noticed that, while DNN is going through its initial load routines, if your website is getting a lot of traffic que'd up, DNN takes longer to load.  I've noticed this on several DNN installs.  For whatever the reason, it happens every time.  

For example, lets say DNN takes 30 seconds to normally load.  On a heavy-load server, if people are attempting to hit the site while it initially loads, it can take 5-20 minutes for DNN to initially load (depending on the amount of people que'd).

A quick and easy fix -  Enable windows firewall to block the initial port while DNN initially loads, then stop blocking the port after your portal loads up.

The goal - scripting Windows firewall.  Does anybody know or have written a program (perl, etc) that will command-line turn off and on a windows firewall exception?  If so, could you share your methods?

Thanks!!

Note:  MS URL to Windows Firewall API:  http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ics/ics/windows_firewall_interfaces.asp

UPDATE 7/31/06:

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 :)

 
New Post
7/24/2006 9:39 AM
 
I'm going to open a GetAFreelancer project to build something like this for a paultry $100 if anybody is interested..  :)
 
New Post
7/24/2006 10:52 AM
 

 

It would be easier (and better form) to direct your traffic to a maintenance page while your site loads.

You could do this by placing a default.html file in your your site's root directory and making it the first default document in your IIS settings.

If you wanted to automate the maintenance page then you could just have a script rename it to turn it on and off.

You may still get traffic from bookmarked links though, so you might also want to replace default.aspx page with your maintenance page instead.

By the way,  I have a new http module that may help a lot with a heavily trafficked site like yours Tim.  It's in beta right now so contact me if you want to try it out.


DotNetNuke Modules from Snapsis.com
 
New Post
7/24/2006 12:09 PM
 
Ya- Although that might work, its really not an optimal solution.  Are you runnig a dedicated server or a site on a shared host?  It would be better to just put DNN in an environment where that can't happen (maybe using some hardware load balancers and such).
 
New Post
7/25/2006 8:59 AM
 
jmitchell wrote

 

It would be easier (and better form) to direct your traffic to a maintenance page while your site loads.

You could do this by placing a default.html file in your your site's root directory and making it the first default document in your IIS settings.

If you wanted to automate the maintenance page then you could just have a script rename it to turn it on and off.

You may still get traffic from bookmarked links though, so you might also want to replace default.aspx page with your maintenance page instead.

By the way,  I have a new http module that may help a lot with a heavily trafficked site like yours Tim.  It's in beta right now so contact me if you want to try it out.



John - Yea I'd be interested in the module!  I'll hit you up on MSN later today.

As far as the maint page, that's a good idea.  Users would see a maint page instead of being completely unable to reach the site.  The only problem is that there has to be zero que on IIS while the .NET CLR loads.  If I have a maint page up, I'm pretty sure people would still be que'd up on DNN's internals while the .net CLR loads, even if I direct it to another default document, and even if I changed the default.aspx.  And if that happens, I'm stuck again with ~15 minute DNN l oadtimes. 

So yea, I really do need to script firewall changes to reduce my 15 minute load times to 30 seconds.  Care to help?  :)
 
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