Extremly long node and doctype save time

[netanel-elipazsoftware]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.2.1

Bug summary

We are experiencing severe performance issues in the Umbraco backoffice, specifically when saving document types and publishing content. The problem is particularly noticeable due to the large size of the umbracoPropertyData table, which contains around 10 million rows.

Publishing content can take between 2 to 10 minutes, causing significant delays.
Saving a document type also takes an unreasonably long time.
The performance bottleneck is making it difficult to progress with the project.
Impact:
This issue is critical, as it significantly slows down development and content management, making it nearly impossible to work efficiently.

Expected Behavior:
Publishing content and saving document types should complete within a reasonable time, even with a large dataset.

Steps to reproduce

1. Take new Umbraco 15 project and import 200K media nodes, then import at least 50K nodes
2. Try to save root node
3. Try to update doctype
   The last section should take long time or even never complete

Video demostrate the time take to save root content node
https://github.com/user-attachments/assets/ae168e56-2242-4bde-9178-92c3c4d840a1

When we inspect the SQL transaction with sql profiler we can see a lot of long process queries like
select * from [cmsContentNu]
and
insert bulk [cmsContentNu] ([nodeId] Int, [published] Bit, [data] NVarChar(max) COLLATE SQL_Latin1_General_CP1_CI_AS, [rv] BigInt, [dataRaw] VarBinary(max))
CmsContentNu (NuCache db table) weight few GB's, very heavy table, it's look like this is the bottleneck

[github-actions]

Hi there @netanel-elipazsoftware!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂