![]() ![]()
We highly recommend you choose Microsoft Graph APIs over CSOM and REST APIs when possible. And in addition to resource unit limits, CSOM and REST are also subject to other internal resource limits, so if applications call CSOM and REST, they may experience more throttling than the limits described in this document. In batching, requests in a batch are evaluated individually by resource units.ĬSOM and REST don't have a predetermined resource unit cost and they usually consume more resource units than Microsoft Graph APIs to achieve the same functionality. The delta request without a token is considered a multi-item query and costs 2 resource units per request. To help applications that follow the guidance, we lower the resource unit cost of delta requests with a token to 1 resource unit, although it's a multi-item query. We reserve the right to change the API resource unit cost.ĭelta with a token is the most efficient way to scan content in SharePoint, and we talk more in details at the best practices for scanning applications. #Syncovery speeding up upload licenseThe table below defines the resource unit limits for an application in a tenant: License count Application’s limits are also defined using resource units. The cost of APIs is normalized by SharePoint and expressed by resource units. ![]() Different APIs have different costs depending on the complexity of the API. Every request that an application makes across all API endpoints, including Microsoft Graph, CSOM and REST, counts towards the application’s usage. In addition to throttling by user account, limits are also applied to applications in a tenant.Įvery application has its own limits in a tenant, which are based on the number of licenses purchased per organization (see the plans listed on SharePoint Limits for licenses included). For example, one user syncing a large amount of data across 10 machines at the same time could trigger throttling. That doesn’t mean that there aren’t other ways to get throttled, just that they’re less common. If you do get throttled, 99% of the time it is because of custom code, such as custom web parts, complex list view and queries, or custom apps users run. The service is robust, and it's designed to handle high volume. That said, it's rare for a user to get throttled in SharePoint Online. Throttling limits the number of calls and operations collectively made by applications on behalf of a user to prevent overuse of resources. #Syncovery speeding up upload codeIf the offending application continues to exceed usage limits, SharePoint Online may completely block the application or specific request patterns from the application in this case, the application will keep getting HTTP status code 503, and Microsoft will notify the tenant of the block in the Office 365 Message Center. Throttled requests count towards usage limits, so failure to honor Retry-After may result in more throttling. In both cases, a Retry-After header is included in the response indicating how long the calling application should wait before retrying or making a new request. The common cause is that the service is experiencing temporary load spikes then expected.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |