Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Remember that your application is not the only one going against the server, so play nice. You may be able to get needed performance in your application but when other applications are going against the server in the real world you may find that the overall experience for all users on that server are poor. I've seen applications which try to consume an insane amount of data at one time because they are only concerned about their performance for the user of their application. Later they find that when many users are using the same application at the same time that the Exchange server involved comes to a grinding halt. Such issues by these applications ore one of the main reasons for all the work on throttling on Exchange. Always keep in mind that throttling is there to help keep proper a reign on applications which would otherwise dominate a server - its your friend. Note though that while throttling has gotten pretty extensive by sure need that it won't account for every performance issue caused by applications and non-performant searches are one of the biggest causes of performance issues with Exchange servers.
Take your time to think of how your building your search and consider the following as each one of these points can have a major impact on performance.
Here are some pointers on searches with EWS:
Exchange Search
https://technet.microsoft.com/en-us/library/bb232132(v=exchg.150).aspx
Message properties indexed by Exchange Search
https://technet.microsoft.com/en-us/library/jj983804(v=exchg.150).aspx
EWS Best Practices - “AllItems” folder
https://blogs.msdn.com/b/webdav_101/archive/2015/05/03/ews-best-practices-allitems-folder.aspxIts extremely important to understand throttling limits which will affect your code should it violate a throttling policy limit.
EWS throttling in Exchange
https://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx#bk_ThrottlingSearch
eDiscovery in EWS in Exchange
https://msdn.microsoft.com/en-us/library/office/jj190897(v=exchg.150).aspx
Exchange 2013: eDiscovery Changes
https://blogs.technet.com/b/johnbai/archive/2014/02/11/exchange-2013-ediscovery-changes.aspx
EWSEditor
https://ewseditor.codeplex.com/
Also see:
EWS Best Practices
https://blogs.msdn.com/b/webdav_101/archive/2015/05/03/ews-best-practices.aspx
EWS throttling in Exchange
https://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx
Repeated calls against the same folder are slow in Exchange Server 2013
https://support.microsoft.com/en-us/kb/3077710
EWS throttling in Exchange
https://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx
Throttling Policies and the EWSFindCountLimit
https://blogs.msdn.com/b/exchangedev/archive/2010/03/12/throttling-policies-and-the-ewsfindcountlimit.aspx
Recommended Mailbox Size Limits
https://blogs.technet.com/b/exchange/archive/2005/03/14/395229.aspx
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in