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...Multiple Instances vs. Multiple PortalsMultiple Instances vs. Multiple Portals
Previous
 
Next
New Post
2/24/2009 9:56 AM
 

We recently made the decision to start create new DNN instances based on the 'function' of the instance.  For example, an instance just serving unauthenticated pages (articles) is its own instance, an instance serving videos is it's own instance, and a community (forum) instance that require a bunch of users is it's own instance.  Why you may ask? Originally it was because of the resource drain on loading all the DLLs for all the modules of a single instance.  The other benefits is the simplicity of upgrading, and scalability on moving 'functions' to different servers.  It has some obvious drawbacks such as custom code to link content from various instances but, we were going to be doing much of this anyway.  Even though I offer the 'why' I'm really interested in feedback on what this does to the server's resources.

Does anyone know how memory, CPU, etc. compare running multiple portals with muliple modules vs. multiple instances running very limited modules, all on a single server? Should each instance have it's on app pool and what's the resource cost of that?

Thanks in advance for any input.

 
New Post
2/24/2009 10:28 AM
 

 Hey Paul,

When it comes to running multiple sites in multiple portals on a single install, we always recommend against it for a number of the reasons that you just mentioned.  Generally the way we calculate server load is by using the following "magic equation".  This is not a completely scientific number because the variables are open to change, but in our expierence, it has held solid:

O(n) = # of Application Pools * # of DNN Installs * (# of Portals per install ^ 2)

The reason that we square the number of portals in the equation is because when you add a portal in DNN, you increase teh amount of load on the database as well as teh amount of data in the database.  As you can see, if you have lot of portals, it grows really big really fast.

Also, something that you'll find is that people seem to be very oppinionated on the whole portal thing.  I know you can find plenty of people out there who say "Portals are the greatest thing ever", however, I work with people on a daily basis who would say "I used to say portals were the greatest thing ever".  In my expierence, many times portals will work ok up until a certain point, then the system will do a crash-and-burn.  I've never heard any horror stories about using multiple installs.

 

 
New Post
2/24/2009 11:31 AM
 

Just another point: one portal to one install means that the portals are all isolated one from another.  If I do something in my portal that brings down the installation, I won't bring down everyone else at the same time.




Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
2/24/2009 3:54 PM
 

Multiple portals will drive up the module licensing costs considerably.


Eric Swanzey
www.swanzey.com
 
New Post
2/25/2009 12:50 AM
 

Paul,

I am evaluating DNN for a large implementation consisting of a single very high volume (up to 10M hits per day) site and a large number (a couple of thousand) of lower volume sites.  The smaller "microsites" typically are displayed in an IFrame on a partner's site.

My question concerns DNNs support for a large number of sites (not sure but I think DNN refers to each of these as a portal).  Sounds like it would be a huge problem in server loading if we ran all the sites on a single instance but running each of them on a separate install doesn't allow us to manage them as a group (and is totally impractical for the number of sites we are talking about!).

Am I missing something?  This seems pretty much like a showstopper for us and I was very much hoping to use an open source solution.

Comments appreciated.

Eric

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Multiple Instances vs. Multiple PortalsMultiple Instances vs. Multiple Portals


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