I have a client who has a few dozen portals set up on one DNN instance.When trying to troubleshoot why the portals were running very slow I found that they have set up DNN in IIS wrong. The set up is this - 1. In IIS they have 1 website- (good so far)2. Under that website they have each portal setup as an application. - (the main problem)3. Each application is pointing to one of a dozen application pools. - (adds to the issue)I have suggested that they change the setup so there is one website that is DNN and then DNN should handle all the work of which portal a person is using. The hangup they have is that by doing website all portals will be under one application pool and if that one application pool goes down then all the portals are down. I have shown them, using process explorer, that each time a portal that is set up as an application is started it loads another instance of DNN into memory but they do not seem to grasp that having DNN loaded 160+ times from one instance of DNN is a problem.Can anyone (maybe on the core team) give me good reasons why their setup is wrong and how I can convince them that the right way is better? Basically they would like some other documentation on the problems the setup they have can and does cause.