And this.. In most cases a web garden will not improve performance and may in fact cause problems such as resource contention. Under normal circumstances they should not be used. There's probably no reason that you would benefit from a web garden. http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/57fd3d02-9b05-4b3f-8c3a-f326ff895ab8.mspx?mfr=true As a best practice, create Web gardens only for Web applications that meet the following criteria: • The application runs multi-instantiated, so that a different instance of the application can be assigned to each worker process. • The Web application is not CPU-intensive. If the CPU is the bottleneck, then adding worker processes cannot help improve performance. • The application is subject to synchronous high latency. For example, if an application calls a back-end database and the response is slow, then a Web garden supports other concurrent connections without waiting for the slow connection to complete.