I work with a number of small business.  I love the DNN framework and use it frequently for small business quick sites.  I have sufferred from some rather slow ( JIT ) load times as great as 20 seconds.  I have a few complaints from clients.  When I discuss this I am told that it is caused by Just In Time Compilers used in Dot.Net tech.  That appears at the surface to leave any hope for improvement out. 

Then working with DNN I find that multiple parent portals handling different sites as a useful way to increase the traffic collectively to the same database engine.  This reduces the engine warm up that kept hitting me in the previous paragraph.  Now however I am having greater login times across the board as if too many domain alias' are causeing me to slow down. 

What does the board find to be the advantages and or disadvantages to the above two approaches.  I would really like your opinion.  Does either improve or reduce my SEO? Does too many Alias cause other issues in modules, upgrades or transferr.  How difficult is it to pull one alias out and make it a dedicated db if needed? 

Ok.... don't know what I want for free. But I appriciate anything yall might have on this one.

Generally speaking I am curious at what point do more records effect my database versus the more traffic keeping my database and DNN Install cached and ready for delivery.  I find the 10 to 15 seconds lost to JIT unacceptable for many of my clients. They complain about the speed of thier sites because of low traffic they are frequently waiting 10 to 15 seconds for thier sites to load.

My other goal in "Stuffing Portals" is to eliminate multiple registrations.  I guess I could use liveid but prefer to manage my user data on my own. I have no problem paying my wel deserved hosting company.  They are the best on the net.  You should know..... ( he he )  User ID : Festus  I think they should adjust thier billing to bill me for resources regardless of stuffed or not. 

Pros

I guess the benifits I have found so far in Stuffing are :

1. Single Login and Registration with a module that allows for portal data sharing. ( DNN Masters )

2. Collective Traffic maintains Cache ready status without having to utilize server trashing keep alive programs.  Inclusive of the rarely visited sites.

3. Allows for more function / purpose specific domain control without addtional web site managmenet of modules.  IE: if I stuff 60 domains on one engine I  update only one module not 60 times.  Less time updateing.

Cons

1. One site goes down they all do. * Usually

2. Module compatability across multiple domains

3. Portability as mentioned by Slavic.

I was not aware that having more than one parent portal would cause slowness across my sites. I am building a club type website with my first DNN site. Thinking down the road and if each club wanted to have its own domain name I was going to make all my sites parent portals.

I will be rethinking this strategy now, this is a big downfall.