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...Portals versus multiple instances on one serverPortals versus multiple instances on one server
Previous
 
Next
New Post
10/31/2008 4:59 AM
 

Does anyone have any experience on the performance difference between running websites as portals on a server versus running it as seperate DNN instances  with  seperate databases on SQL 2005, but under one application pool. 

 
New Post
10/31/2008 5:27 AM
 

the difference in performance depends on your hardware specifications, a multiportal installation requires less resources (RAM, HDD and database) and single startup time, but is less flexible when restore from backup is needed or there are specific configuration requirements for the installation by a single portal.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/31/2008 8:01 AM
 

It really depends on what you are needing to acheive also the separtation to multiple instances can often make it easier when dealsing with portals that have specific modules in use that don't play well with others.

In one the main installations I'm responsible for an instance with 50+ Portals. Each being administered by different individuals and with traffic on them of 30000+ per month on a couple of the portals.

We do run separate instances for internal applications and for bespoke modules that we're unsure of the stability of. If we are really unsure of stability however we run the instance in a separate app pool.

But in answer to your question the perfomance difference between running instance under one app pool and a multi portal site has been fairly negligible right now, but from an administration perspective being able to traverse all the sites witha single host login saves a lot of time. What was mentioned about backing up separate site does hold true however and I have yet to find an effective way to get around this in a multi portal situation. I simple backup the database and the entire application.

Kind Regards

John

 


John Nicholson
 
New Post
10/31/2008 10:01 AM
 

Thanks for the response. My biggest motivation for running installations as seperate instances would be as you said a) ease of backup and restore. I have experience where a user destroyed certain information for a specific portal and later request a restore. In a portal environment it is impossible as I will then have to restore other clients' portals as well - destroying their new data  b) certain modules running in certain portals have not been upgraded to latest version and I am concerned with version clashes and c) Some clients would like to know that they can move an installation if unhappy with our service and d) we are in South Africa and sometimes do sometimes physical development with our clients in a rural environment with no or slow access to datalines. We therefore have to develop on a development machine and then port the application to a live server. I am not sure in such instance if the method of exporting and importing a template will resolve this issue.

I am currently in the process of implementing a new rack server at a web farm (Core 2 Quad  2.40 GHz 8Mb OD Cache  with 2 GB ram) and is not 100% convinced if I should follow the portal of seperate instance route. The one login across multiple portals is not critical to me, but if there is serious performance issue I will definatedly consider going portals.

Regards

Armand

 
New Post
10/31/2008 10:57 AM
 

I can say from experience that import and exporting templates is not a method I would rely upon. There is no major issue with multiple instances, are you running your SQL server of the same box or is that hosted elsewhere?

Given what you've described I personllay would suggest going multiple instances and I know that that appraoch is taken by an overwhelming number of people within the dnn community. primarily for the Reason stated above of data separation.

FYI I'm running the dnn instance on a VM allocated 2GB ram and 2 logical cores. this also runs SQL server express though I have set this up in a manner similar to a full installation of SQL server. This system has had no major problems.

Regards

John


John Nicholson
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Portals versus multiple instances on one serverPortals versus multiple instances on one server


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