Adding a new property to doc type is extremely slow (or gets stuck)
Sometimes adding a new property to a doc type, or changing order or renaming the property and then clicking on Save doc type button breaks - I mean the button displays loader forever, and I mean eg. 10-20 minutes.
When I refresh the page displays various errors.
So it looks like the saving does not finish. Or simply gets stuck as I have no idea if it would ever finish.
I've had a similar issue for a number of weeks now and I'm still trying to find a solution, however, I have found some error logs in my SQL Server locally which lead me to try this:
Looking at your stack trace Owain, your error, talks about a timeout to SQL during the running of the DocumentVersionRespository Application.
This service runs on a timer, so it might explain why it's intermittent, eg you might just be unlucky when you change your backoffice thing and this is running.
Probably the version cleanup is a long running task and locks SQL.
People say when they have it, they restart SQL etc, and this would clear that lock/task...
be interesting to turn it off (probably don't need it during development anyway?) - and see if you experience the problems again...
...eg I am just making a guess and possibly jumping to conclusions!!!
I am wondering whether we should have version's EnableCleanup on on the pulic site and how this will behave. As we didn't publish the site yet.
Also still the CMS is slow in places, for example when loading the page the top navigation and left panel with the content nodes takes sometimes several minutes to display. So no way to navigate until they are loaded.
Also the translations tree is very slow in expanding if we have loads of items beneath the top folders. The previous versions didn't have this problem and everything was loading pretty fast
Although it happens only on the first load and then it is probably cached and expands and navigates through translation items normally.
It looks like the issue for me was lack of memory on my laptop - when it happened this morning I opened up Task Manager and saw that my laptop was running 95% memory usage.
I killed off a few programs and things save super quick again.
Adding a new property to doc type is extremely slow (or gets stuck)
Sometimes adding a new property to a doc type, or changing order or renaming the property and then clicking on Save doc type button breaks - I mean the button displays loader forever, and I mean eg. 10-20 minutes. When I refresh the page displays various errors.
So it looks like the saving does not finish. Or simply gets stuck as I have no idea if it would ever finish.
It is unacceptable.
Basically the same issue in v9 and v10
Hi Nick,
I've had a similar issue for a number of weeks now and I'm still trying to find a solution, however, I have found some error logs in my SQL Server locally which lead me to try this:
https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows?view=sql-server-ver16
I've only made this change today, so I'm still to find if it's a permanent fix or not but thought it might help.
I'll be following this to see if anyone else has similar issues.
O.
Update - that SQL server update hasn't fixed my instance after all. It must have just been a help that I restarted SQL server at some point.
It's as if SQL locks itself and never recovers.
Just changed the order of two properties on a Docuement Type, got the spinnning green save button and then got this error :
O.
Hi Owain/Nickornotto
Does it still occur if you turn off ContentVersion cleanup?
https://our.umbraco.com/documentation/Fundamentals/Data/Content-Version-Cleanup/
Looking at your stack trace Owain, your error, talks about a timeout to SQL during the running of the DocumentVersionRespository Application.
This service runs on a timer, so it might explain why it's intermittent, eg you might just be unlucky when you change your backoffice thing and this is running.
Probably the version cleanup is a long running task and locks SQL.
People say when they have it, they restart SQL etc, and this would clear that lock/task...
be interesting to turn it off (probably don't need it during development anyway?) - and see if you experience the problems again...
...eg I am just making a guess and possibly jumping to conclusions!!!
regards
Marc
I have turned version cleanup off and will monitor if this makes a difference.
It seems to have improved with this option off.
I am wondering whether we should have version's EnableCleanup on on the pulic site and how this will behave. As we didn't publish the site yet.
Also still the CMS is slow in places, for example when loading the page the top navigation and left panel with the content nodes takes sometimes several minutes to display. So no way to navigate until they are loaded.
Also the translations tree is very slow in expanding if we have loads of items beneath the top folders. The previous versions didn't have this problem and everything was loading pretty fast Although it happens only on the first load and then it is probably cached and expands and navigates through translation items normally.
It looks like the issue for me was lack of memory on my laptop - when it happened this morning I opened up Task Manager and saw that my laptop was running 95% memory usage. I killed off a few programs and things save super quick again.
O.
I see that Umbraco is more fast on SqlLite than SQL Server.
is working on a reply...