ServiceThrottle Class
Controls the throughput of a service to optimize availability and performance.
Assembly: System.ServiceModel (in System.ServiceModel.dll)
| Name | Description | |
|---|---|---|
![]() | MaxConcurrentCalls | Gets or sets the maximum number of messages actively processing across all dispatcher objects in a ServiceHost. |
![]() | MaxConcurrentInstances | Gets or sets the maximum number of service objects that can execute at one time. |
![]() | MaxConcurrentSessions | Gets or sets a value that specifies the maximum number of sessions a ServiceHost object can accept at one time. |
| Name | Description | |
|---|---|---|
![]() | Equals(Object) | Determines whether the specified object is equal to the current object.(Inherited from Object.) |
![]() | GetHashCode() | Serves as the default hash function. (Inherited from Object.) |
![]() | GetType() | |
![]() | ToString() | Returns a string that represents the current object.(Inherited from Object.) |
Use the ServiceThrottle to tune the performance characteristics of a service. The easiest way to configure the ServiceThrottle for a service is to use the ServiceThrottlingBehavior, especially from an application configuration file.
The MaxConcurrentCalls property specifies the maximum number of messages actively processing across all the dispatcher objects in a ServiceHost object.
The MaxConcurrentInstances property specifies the maximum number of InstanceContext objects in the service.
The MaxConcurrentSessions property specifies the maximum number of sessions a ServiceHost can accept.
Note |
|---|
A trace is written when the first call, InstanceContext, or session is queued on the waitlist. The first trace is written as a warning. |
The following code example shows the typical use of the ServiceThrottle by referencing the ServiceThrottlingBehavior in an application configuration file. In this case, the values that are specified establish, at most, one message processing at one time from one connection to one InstanceContext. Real-world usage must be determined through experience.
Available since 3.0
Any public static ( Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.


