Performance issue

[inmetatosu]

Hi,

If there is a large number of categories with multiple levels, performance is seriously affected when loading the category tree.
Could you look into this?

Regards,
Torunn

[Eric-4NG]

Same here, for every sub-category a XHR request is fired. Would be nice if it could be loaded with a single request, or paged? Less stress and the browser will handle it easier as well I assume.

[alasvant]

Same here, category has 70 children and occasionally it leads to situation that we don't get category picker correctly populated as some of the XHR requests will return 500 or 502 (DXP env CloudFlare). DXP log stream shows that database gives timeout.

[Eric-4NG]

After dirty work-arounds to load the items one request at a time, it still times out.
Eventually we ended up here:
https://support.optimizely.com/hc/en-us/articles/4432366206733-CMS-12-site-crash-due-to-SQL-timeout-error-when-working-in-CMS-edit-mode

After requesting what the recommended value is for this, Optimizely Support suggested to turn MARS off. So that is what we've currently done. But we still have to monitor the effects of this change. But you could give that a try as well.

[Eric-4NG]

Turning MARS of was not the solution, did no harm either for anything else.

In the meanwhile we've played around with increasing the SQL plan on Azure. Which helped a little, then we've played around with threadpool settings in runtimeconfig.template.json did no harm, but did not solve it either.

We're now running SQL index reorganize/rebuild periodically. That seems to be quite helpful to resolve it. It will not load instantly, but it seems to run stable for now without restarting the site by the amount of requests executed.