Bug 1046270

Summary: Performance improvement when indexing updated nodes
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Horia Chiorean <hchiorea>
Component: ModeShapeAssignee: Horia Chiorean <hchiorea>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: high    
Version: 6.0.0CC: drieden, fnguyen, ldimaggi, rhauch, vhalbert
Target Milestone: CR2Keywords: QA-Closed
Target Release: 6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When using a hierarchical database repository with indexing enabled, if a node is updated with property changes only, all the node's children will be reindexed. This has a significant negative impact on performance.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:50:13 UTC Type: Support Patch
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Horia Chiorean 2013-12-24 10:02:00 UTC
In a repository which has indexing enabled, when a node is being updated and only has property changes, the current code will reindex all the node's children.

This is a bug which, once fixed, should (significantly) improve performance in this scenario because the only case when after a node update the children of this node should be reindexed is when the path of the parent node has changed. In all other cases the children should never the "touched" .

Comment 1 Horia Chiorean 2014-01-03 07:13:25 UTC
This is a critical performance improvement which should be part of the first DV rollup patch.

Comment 3 JBoss JIRA Server 2014-01-07 17:45:51 UTC
Randall Hauch <rhauch> updated the status of jira MODE-2124 to Closed

Comment 4 belong 2014-01-08 06:17:31 UTC
Horia confirmed fixed for CR2 - setting to requires_doc_text- accordingly.