Edit

ProcessModelSection.MaxWorkerThreads Property

  • Reference

Definition

Namespace:
System.Web.Configuration
Assembly:
System.Web.dll

Gets or sets a value indicating the maximum amount of worker threads per CPU in the CLR thread pool.

public:
 property int MaxWorkerThreads { int get(); void set(int value); };
[System.Configuration.ConfigurationProperty("maxWorkerThreads", DefaultValue=20)]
[System.Configuration.IntegerValidator(MaxValue=2147483646, MinValue=1)]
public int MaxWorkerThreads { get; set; }
[<System.Configuration.ConfigurationProperty("maxWorkerThreads", DefaultValue=20)>]
[<System.Configuration.IntegerValidator(MaxValue=2147483646, MinValue=1)>]
member this.MaxWorkerThreads : int with get, set
Public Property MaxWorkerThreads As Integer

Property Value

Int32

The maximum number of threads. The default is 20.

Attributes
ConfigurationPropertyAttribute IntegerValidatorAttribute

Examples

The following code example shows how to access the MaxWorkerThreads property.


// Get the current MaxWorkerThreads property value.
int maxWorkerThreads = 
    processModelSection.MaxWorkerThreads;

// Set the MaxWorkerThreads property to 128.
processModelSection.MaxWorkerThreads = 128;

' Get the current MaxWorkerThreads property value.
   Dim maxWorkerThreads As Integer = _
   processModelSection.MaxWorkerThreads

' Set the MaxWorkerThreads property to 128.
processModelSection.MaxWorkerThreads = 128

Remarks

The value of MaxWorkerThreads must be equal to or greater than the MinFreeThreads setting in the httpRuntime configuration section.

You can have some control over the CPU utilization by setting the number of worker threads and I/O threads, using the MaxWorkerThreads property and, the MaxIOThreads property, respectively.

The difference between the two types of threads is that the latter are bound to I/O objects, such as a stream or a pipe, and the former are traditional unrestricted threads. For Internet Information Services (IIS) version 6.0 and higher, ASP.NET processes requests on worker threads. This is because ASP.NET is integrated within IIS.

These threads are obtained from the process-wide CLR thread pool belonging to an application.

Note

Usually the default values for the allowed threads are sufficient to keep the CPU utilization high. If for some reason your application is slow, perhaps waiting for external resources, you could try to increase the number of threads to a value less than 100.

Applies to

See also