As applicable, this article also identifies differences in throttling policies in different versions of Exchange.ĭefault throttling policy, access to throttling policy, and throttling policy configuration differs between Exchange Online and Exchange on-premises. This article identifies the different throttling policies and service limits for EWS, whether you are targeting Exchange Online or versions of Exchange on-premises starting with Exchange Server 2010. When you design applications that use EWS, it is important to account for throttling policies, to help ensure application reliability and the health of your Exchange server. The result is that a user may be within their throttling limit and still experience slowdowns until the health of the resource is back to operational levels.Įach client access protocol in Exchange, including EWS, has a throttling policy. When high load factors are detected that degrade the performance of these resources, EWS connections are throttled proportionally based on the amount that each caller has contributed to this high load condition. Exchange constantly monitors the health of critical infrastructure resources, such as mailbox databases. Throttling is a reactive response to overuse of system resources that may affect service reliability and functionality. Throttling in Exchange helps to ensure server reliability and uptime by limiting the amount of server resources that a single user or application can consume.
The article provides information about EWS throttling in Exchange Online, Exchange Online as part of Office 365, and on-premises versions of Exchange starting with Exchange 2010. Provided by: Glen Scales Michael Mainer, Microsoft Corporation Learn about the throttling policies that affect EWS when you are using Exchange.
0 kommentar(er)
