I have my DNN instance on a dedicated server with multiple processors and was wondering about utilitizing the server's full resources to make DNN uber fast.  DNN is the only application I have running on the server, so I don't need to worry about anything else messing with it. 

I had been reading about (never knew this before) the machine.config and the processModel section where you can set to have the ASP.NET process use multiple processors.  I had always assumed it already did and so never really looked into this before.  At any rate, I configured my machine.config to have webGarden="true" and set the mask to allow use of all processors (in this case, just 2).

Next, I modified my web.config to allow storage of the sessionState in the ASP.NET session state server (apparently the default web.config for DNN was devoid of any entry for that at all, so I had to add it).

At first, it all seemed to be working fine, but then came screeching to a halt and *if* it would access at all, was getting a general "dotnetnuke timeout".  I put everything back the way it was, tried resetting IIS and application pool, and it still had issues.  I reboot the server and now it is back up and running again.

Question is, can I not run it with multiple processors?  Or beyond that, if I can, what the heck did I do wrong?

Oh, that makes me sad.  But at least I understand what happened and won't do it again.  Thanks for the heads up.

This actually brings up a very interesting question -- can i have webGarden enabled on a server with multiple applications but disable it on a per-application basis?  My thoughts are "no", since the processModel attribute is not allowed within a web.config.  Obviously on my server for DNN this wouldn't be an issue, but I have applications that I use on another server that might benefit from multiple-core processing.

Thanks for the quick response though, and it makes perfect sense.  I do have multiple items in the scheduler that run every couple minutes and of course, hundreds upon hundreds of pages that need to deal with caching... so, that explains it very well.