Another cause can be an overload of tenants sharing the same Office 365 infrastructure, an issue that can lead to crowded servers. Though it’s typically the culprit, throttling does not only happen due to high call volume on your tenant. ![]() Servers can easily become unresponsive or even crash without this mechanism! 429 errors or “Server too busy” messages). Office 365’s way of protecting itself is to “throttle” the traffic, which means stopping users from making these calls. These calls are unpredictable and hard to plan for on the database side since Office 365 doesn’t necessarily know when users are going to perform an action like a full backup or a security search that needs to touch almost every object in SharePoint. ![]() Regardless of what entry-point in Office 365 we use ( Graph, CSOM, etc.) those calls are turned into SQL queries or calls to lower-level infrastructure which quickly ramp up the CPU usage on that server. Another thing to consider is that throttling is normal and is merely a result of Office 365 ensuring that it can keep the system healthy and fast for its users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |