I'm looking for some "best practice" info regarding the hosting of dotnetnuke websites.  I know DNN is capable of hosting hundreds of websites within the same Portal framework/database instance.  However, I'm seeing on my Server that each instance consumes about 50 MB per website.  Thats a lot if you are hosting a fair number of sites.  This seems excessive.  Maybe my expectations are too high -- I don't know.  Does anyone have any tuning tips on configuring DNN and IIS to get the best performance/site/Server?  Thanks.

I agree.  Most of the portals I host are shared in the same install -- I started noticing the IIS worker process steadily climbing to >500MB at which time DNN began to be unresponsive for all Portals.  Now granted I could increase the resources on the server, but it just doesn't seem right.  I've since separated each website into it's own shared pool to determine which site is the culprit.  Now everything is running much more smoothly, but I imagine each site with it's own shared pool has an associated overhead as well.  The sum of the memory consumed from each IIS process is about the same as when they were all lumped into the same pool.  Only now I can see at a glance where the largest load is coming from.  And in fact it may be a little less than before.  It seemed like the aggregate overhead from all sites sharing the same pool was pulling everyone down.  At first I thought there was possibly a memory leak with one of the modules, but now with each site in isolation from the others (even though they share the same portal) I don't see the steady climb of RAM consumed as before.

Anyway, still looking for best practices and experiences from other users.

Regards.

Hmm...now that's interesting.  I hadn't considered that having unused skins, containers, images and documentation files would have any effect on the DNN footprint (other than consuming storage space on the hard drive).  So are you saying that while additional skins, containers, etc. the are not actively being used, but still contained within the DNN "tree" may have an impact on performance?  How so?  In guessing I would say that perhaps on the admin side DNN must scan those directories to load up the list of skins and containers available, etc, but that seems pretty minimal to overal performance on the server.

Any other Server/DNN tuning guidelines?