In this post I will discuss about the Rate-Based Throttling and Orchestration Throttling. Please refer the previous post for the General Setting and Resource-Based Throttling @ host level.
Rate Based Throttling
Rate-Based Throttling allows you to configure rate-based criteria when the host will go into a throttled mode.
The Publishing portion refers to the rate at which messages are published from this host (to downstream hosts).
The Delivery portion refers to the rate at which messages are delivered to the orchestration or messaging engine (within this host).
This set of controls lets you determine what will be the definition of too great a mismatch between inflow and outflow and what will be the resulting action.
Specifically, Minimum Number of Samples and Sampling Window Duration work together to define how much traffic will be observed to determine real operational rates.
Rate Overdrive Factor refers to the allowable mismatch in the producer/consumer relationship.
Maximum Throttling Delay is the maximum delay BizTalk will impose (at highest severity throttling).
Throttling Override allows you to manually introduce throttling, or disable it altogether. If you manually introduce it, Throttling Override Severity allows you to control the severity level for that case.
Orchestration Throttling allows for fine-grained control over dehydration/rehydration.
When Dehydration Behaviour is set to Custom, the Maximum Threshold is used to determine the maximum idle time (blocked and waiting for a message) before dehydration, and Minimum Threshold sets the minimum idle time. You can see by default the minimum is 1 second and the maximum is half an hour.
If you check the Subscriptions check box, you are overriding the behaviour of when the MessageBox will decide to pause/resume moving messages to the subscription instance based on the number waiting to be consumed.