Article ID: 911716 - View products that this article applies to.
When you host Web applications that use Microsoft ASP.NET on a computer that is running Microsoft Windows Server 2003, you may experience decreased performance. This issue may occur when you host the Web applications in multiple application pools on a multiprocessor computer. Additionally, you may experience one or more of the following issues when available memory is low:
These issues occur because the Microsoft .NET Framework common language runtime (CLR) uses the Server garbage collector (GC) on multiprocessor computers. This is the default behavior. The Server garbage collector is optimized for scalable throughput on multiprocessor computers. To reduce contention and to improve garbage collector performance on multiprocessor computers, the Server garbage collector creates one heap per processor for parallel collections. Therefore, the Server garbage collector consumes lots of memory when you host multiple ASP.NET worker processes. This behavior may cause the issues that are described in the "Symptoms" section.
To work around these issues, configure the .NET Framework common language runtime to use the Workstation garbage collector. The Workstation garbage collector is optimized to reduce garbage collector pause times for interactive applications. Additionally, the Workstation garbage collector creates only one heap. Therefore, the Workstation garbage collector uses less memory when you run applications on multiprocessor computers.
To configure the .NET Framework common language runtime to use the Workstation garbage collector, add the following code after the <runtime> element in the Aspnet.config file. The Aspnet.config file is located in one of the following folders:
Note The Workstation garbage collector is optimized for low latency. Low latency is typically required for client applications. However, low latency may cause decreased throughput after you configure the .NET Framework common language runtime to use the Workstation garbage collector.
For more information about performance considerations in the .NET Framework, visit the following Microsoft Developer Network (MSDN) Web site:
Article ID: 911716 - Last Review: December 3, 2007 - Revision: 1.6