Memory recycling is the equivalent application pool setting for the memoryLimit ASP.NET process model setting. It specifies the maximum amount of memory that a worker process can use. If the worker process exceeds this amount, a new process is created to replace it, and all current requests are reassigned to the new process. There are two important differences between the memoryLimit ASP.NET process model setting and the Memory recycling application pool setting:

• The memoryLimit ASP.NET process model setting only uses physical memory. The Memory recycling application pool setting allows you to specify separate limits for physical memory and virtual memory. Physical memory (or a combination of both physical and virtual memory) is commonly used for ASP.NET applications because of the way the common language runtime's garbage collector works. Virtual memory is commonly used for classic native applications that fragment the heap.

• The Memory recycling application pool setting is specified in megabytes, not as a percentage of the total memory.

Recycle worker process is the equivalent application pool setting for the requestLimit ASP.NET process model setting. It specifies the number of requests that cause a worker process or application pool to be recycled. Recycle worker process is disabled by default. To enable Recycle worker process, select the check box and specify the number of requests in the spin box.

Recycle worker processes is the equivalent application pool setting for the timeout ASP.NET process model setting. It specifies the interval at which to recycle a worker process or application pool. Recycle worker processes is enabled and set to 120 minutes by default. You can specify a different interval by changing the value in the spin box. To disable Recycle worker processes, clear the check box.

Tasks

Reference

Concepts

Other Resources