Has anyone experienced performance issues with SharePoint Online account aggregation? In a sandbox environment, it aggregated 243 accounts in 17 minutes. However, in production, it takes an excessive amount of time and eventually gets terminated automatically, prompting the system to restart the aggregation process. I’ve noticed that CPU usage spikes significantly when this task begins. I’m unsure of the cause, but I believe our aggregation settings are fairly straightforward. Does anyone have any insights?
Thanks for sharing that. I checked the VAs in the cluster and all seem up to date. But this time, I was able to aggregate some accounts, and after a while the aggregation stopped again and the aggregation failed one more time. And I could not anything in the VA Troubleshooting guide.
Now we can go in the following way of identifying the issue:
i. Is there latency between the VA and Sharepoint found which you can leverage the toolbox service and its cmdlets present in the troubleshooting guide.
ii. Then to increase the IQService timeout for the source. Usually when aggregating large dataset it is helpful to increase the timeout from default value of 30 secs to maybe 45 seconds and check the difference.
Additionally what I have observed is to have two different IQService installations to cater to Active Directory and SharePoint online sources as it is easier for the service to handle the aggregation and prov/deprov activity if applicable.