So I upgraded my clients Umbraco 13 to 14. Today I had a meeting and their team was furious of me and what I have done to administration. Slower interface, occasionally poping Content not found before displaying Node Content, sluggish login, etc., are just some issues they brought up. I have tried myself and v13 was a breeze compared to v14. Its same server and everything from v13. Is there any way can match performance of v13? Are there any such plans?

Hi, I'm interested in hearing more about this. Which specific version are you on? How many nodes in the content tree do you have? Any extra caching mechanisms enabled? Any other info you could possibly give us?

@Jacob Overgaard everytime you open up list node with 2000 items it displays message of not found content, then content appears in a half a second. Have you tried performance of v13 vs v14? Upgrade same site and give it a try. I tried clean install and added few nodes, added few content pages, upgraded to v14.2 and navigating in between pages is huge drop in UI UX experience.

Yes, I have tried it and I might be a little biased, but I'm trying to understand the statistics of your site to get some reproducible data. If I understand you correctly, you have one node (like a root node?) with 2000 items, which you have configured in a list view, is that correct? Is it safe to assume that the network requests (you can see those in your browser's DevTools) are not running slowly, but in fact it is the UI that is rendering them slowly?

Yes, node Posts that has like 2000 posts is now way slower to list first 100 posts. Same site on v13 was way faster, and each and every time my client user are afraid of messages, content not found (they deleted node once, and got same message). Can that nasty message "Content not found" be handled better?

Are you sure there isn't something referenced by the node-with-2000-children or one of its 2000 children that doesn't exist? I think I've seen that behavior in v14; a broken relation or a broken link of some kind. v13 and below usually don't make not-found toasts when this happens, only for custom "unhandled" backoffice API exceptions. If you check F12, can you see which content is giving the Content Not Found? It could be an in-plain-sight 404 to the backoffice APIs.

@kdx-perbol this could be due to my other thread "Nodes entered programmatically " with 0 issue.