IIS Sound Application Pool Settings

Application Pools
Recycle tab of the Properties dialog box

Memory Recycling

"Memory Recycling" is the Application Pool
setting equivalent to the memoryLimit
ASP.NET Process Model setting. It specifies the maximum amount of memory that the worker process can use. If the secondary process exceeds this number, 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 settings and the Memory Reclaim Application Pool
settings:

Recycling Auxiliary Process

Recycling Auxiliary Process is equivalent to requestLimit
Application Pool for ASP.NET Process Model Settings
Settings. It specifies the number of requests that caused the worker process or application pool
to be reclaimed. The Recycle Auxiliary Process is disabled by default. To enable the Recycle Auxiliary Process, select the check box and specify the number of requests in the Value adjustment box.

Recycling multiple worker processes

Recycling multiple worker processes is equivalent to timeout
application pools for ASP.NET process model settings
> Settings. It specifies the time interval for reclaiming the worker process or application pool
. By default, Recycle Multiple Secondary Processes is enabled and is set to 120 minutes. You can specify a different time interval by changing the value in the value adjustment box. To disable Recycle multiple worker processes, clear the check box.

Performance Application Pool
Settings

The performance of the auxiliary process can be controlled by the performance Application Pool
setting. The following sections describe how to specify performance application pool
settings.

Specifying Performance Application Pool
Settings

Performance Application Pool
Settings are in the Properties dialog of Application Pool
Specified in the Performance tab.

Set Performance Application Pool
Settings

Application Pools
"Performance" tab of the "Properties" dialog box

Network Park

"Network Garden" is equivalent to webGarden
and cpuMask
Application Pool
settings for ASP.NET Process Model Settings. To enable Network Park, set the Maximum number of worker processes to a value higher than 1. This value also determines the maximum number of processes for the Application Pool
.

Because the network garden supports the use of multiple processes, each process has its own copy of the application state, in-process session state, cache, and static data. Network gardens should not be used for all applications, especially if they require maintenance. Be sure to check the performance of your application before deciding whether the network garden mode is applicable.

When using the Network Park, it is important to understand the state of the session and the way it works. It is also important to consider how other application pools
settings affect the application.

Session State in Network Park Using Secondary Process Isolation Mode

When using session state, be aware that the worker process isolation mode does not support passing requests back to the process that caused the request to return. When an application is running in a network park that is in an ASP session state or application state, the application needs to send its request back to the originating process. When using the IIS 6.0 Application Pool
, make sure that the application keeps a connection open so that its request is sent back to the appropriate process. If this connection is not left open, the request will be sent to the next available worker process that serves the network garden.

Cycles in a network garden using worker process isolation mode

A loop is a load balancing method for applications. As each request arrives, it is automatically sent to the next available process. For example, if the network garden has 4 processes, the request is sent to processes 0, 1, 2, and 3 and sent in this order. Then repeat the loop for other requests.