jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christoph Kiehl <ki...@subshell.com>
Subject Re: Performance problem with references
Date Tue, 12 Sep 2006 12:01:40 GMT
Michael Neale wrote:

> I gather you are referring to saving the node that has all the 
> references as
> attributes?
> ie:
> NodeA ---> NodeX *
> Where there are 100 000 NodeX instances. NodeX.getReferences() would then
> return just one NodeA (in this case).

No, my scenario is the following:

NodeA * ----> NodeX

NodeA is one of 100.000+ documents referring one NodeX which is a state (e.g. 

If you have a look at the persistence manager interface you will recognize that 
not only the reference property of NodeA is saved but also the set of references 
to NodeX (which in this case are 100.000+ references). This set gets updated 
every time you add a reference to NodeX anywhere in your repository.

As Tobias described, this behaviour is expected. It gives you good performance 
on node.getReferences() calls.


View raw message