How does a web garden help you to utilize more CPU?  The only time I can think of that it might help is if you are bottlenecked in the request pool, which is pretty hard to do without running the CPU up.

If you have large uploads or other processes that will require requests to run for relatively long periods of time then you might have a reason for using a web garden, but there is a trade-off there too.
This is because if you start running multiple worker processes in the same application pool then you are going to be more likely to run into contention on the outside resources like shared files.

Another reason to run a web garden would be to have redundant processes in case one becomes deadlocked.  ASP.Net already handles deadlocked worker processes by recycling them automatically, and if you are wanting real isolation between different applications then they should be in their own application pools.

Long story short.  The trade-offs for running in a web garden are likely not worth it in most web applications.

Thanks. John, the mulitple application pools is what we tried several months ago...remember? I thought that might a good idea but I am not complaining about performance at this moment. To be honest, I am very happy with DNN as it runs now on my site.