U4-4465 - Deleting Property Takes Too Long (10 Minutes)

Created by Nicholas Westby 18 Mar 2014, 16:54:52 Updated by Shannon Deminick 26 Jun 2017, 05:41:32

Relates to: U4-4276

I have a site that uses about 1,000 content nodes. About 700 of those nodes are of a single document type (Product). When I delete a property from that document type (in the Settings section of Umbraco), the CPU on the server is pegged at 100% and the disk write activity increases dramatically (varies between 3MB-12MB per second) during that time.

I have a couple Examine indexes. I'm guessing when I delete a property, Examine reindexes all that content, which I suppose is the reason for the CPU/disk activity. Problem is, after I click the "X" to delete the property and confirm the dialog, the property doesn't show as deleted until I reload the document type in the UI.

If this is caused by Examine/Lucene, shouldn't that be done in the background? Also, maybe this is actually caused by the extremely slow ContentService, but I'm not sure.

Comments

Nicholas Westby 18 Mar 2014, 17:28:10

Correction, this is Umbraco 6.1.6, not Umbraco 7.0.4 (I am working with multiple versions).


Shannon Deminick 10 Sep 2014, 01:43:16

I think you should upgrade to the latest 6.x version and check if it's still an issue and if so please let us know, there's been some updates regarding the content xml cache, namely:

http://issues.umbraco.org/issue/U4-3145 http://issues.umbraco.org/issue/U4-3091 http://issues.umbraco.org/issue/U4-3787 http://issues.umbraco.org/issue/U4-5121

Examine does do reindexing on a background thread, though this doesn't mean that it won't still use CPU.

Part of the problem is with the Umbraco Apis and the amount of querying/updating it needs to do, for this process, it needs to update every record in the cmsContentXml table to reflect the new xml structures, then it needs to update the actual xml cache structure. This same process is true for renaming property type's and content type's.

There's been some API performance updates in the 7.2 branch that may assist this but I'd need to run some tests.

Please let us know if the performance of this is fixed/better/the same in the latest 6.2.x release.


Shannon Deminick 26 Jun 2017, 05:41:32

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Normal

Type: Performance Problem

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.1.6

Due in version:

Sprint:

Story Points:

Cycle: