Hi, On Mon, Sep 27, 2010 at 2:10 PM, Seidel. Robert <[email protected]> wrote: > The problem is the create of new child nodes. Maybe in our example the second > level node a0 does not exist. What Jackrabbit does is adding the a0 node to > the 3d node and storing the 3d node and all its children (NodeStateEx > store(NodeState state)). If you have 100 children, then Oracle needs some time > to read all these children just to figure out, ups 99 of these already exists. > > So, the performance can go down from time to time, until the whole structure > is created. > > A better way in this case would be to store only that special child node and > the parent.
Sounds correct to me. Can you file an improvement request for this? Do you have ideas on how to implement such an improvement? I guess the key method to modify is InternalVersionManagerBase.getParentNode(). BR, Jukka Zitting
