-
Enhancement
-
Resolution: Done
-
Critical
-
3.8.0.Final, 4.0.0.Alpha4
hchiorean writes (initially in MODE-2276):
In writing some more tests and looking at performance data while adding nodes, I found another potential significant bottleneck not only for adding nodes but also for setting properties: AbstractJcrNode#isCheckedOut (called both from #addNode and #setProperty). This is especially visible when running a deep hierarchy of nodes, where this method will load the entire hierarchy of parents for a child node, no matter how deep.
Is there any way we can optimize this (e.g. store some sort of boolean flag each time we check out a node, so that we can easily compute the checked out status of a path. Or looking at the node types for mix:versionable) ?
- causes
-
MODE-2642 Node.isLocked() within a transaction returns false for a locked node
- Resolved
- is related to
-
MODE-2109 Support nodes with a very large number of unordered and uniquely-named children
- Resolved
-
MODE-2271 Improve performance of getting path of node that is below a large ancestor
- Resolved
-
MODE-2266 Create simple scalability and performance tests
- Resolved
-
MODE-2276 Improve performance of adding node under parent
- Resolved