Forum Discussion
Inconsistent behavior in using Taxonomy API
Hi Paul this sounds like a SharePoint timer or indexing issue. Some things to try out and test:
- How many terms are you loading or creating? Try reducing the number as see if that resolves the issue.
- How often are you running this solution? Try reducing the number of runs and see if that resolves the issue.
If either of the above resolves the issue there are 2 ways off the top of my head for handling this:
- Easiest solution is to “throw more power at it”. Increase the RAM and / or processors and / or disk speeds and see if it can handle large loads.
- Alternatively, evaluate the SharePoint timer and indexing jobs if you can. You may be able to increase the frequency. Alternatively, this should give you clues on the delays you may need to add to your code to properly pause the record passing. If you are bound to the speed of the SharePoint, then coding to pause to those speeds is the best you can do.
Hope these ideas help and there may be more. If you need assistance, my company specializes in these things and may be able to help. https://www.eswcompany.com/sharepoint-consulting-2/.
- paulpaschaApr 20, 2018Bronze Contributor
Hi Joel,
Thanks for your response! Sorry I forgot to mention the environment I'm working in is SharePoint Online so no option to increase hardware.
The logic is running in an Azure Function App by queueu-triggered Functions. I have also written some Unit Tests where I see the same happening (e.g. Unit Tests succeed most of the times, but frequently fail due to one of the errors liststed above). Very unpredictable...
- Joel HillApr 20, 2018Brass Contributor
Ahh yeah there is a max memory usage on functions, but I doubt you are hitting it with taxonomy changes. Similarly though if you are using large amounts, try scaling down the load and see what happens. A bit painful for performance testing unless you have some "real" performance testing tools at your disposal that play nicely with Azure. Good luck or hopefully someone can give a better answer than me!
Max: 1,536MB
Source: https://azure.microsoft.com/en-us/pricing/details/functions/