jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Neale" <michael.ne...@gmail.com>
Subject Re: Performance problem with references
Date Tue, 12 Sep 2006 13:23:41 GMT
right, so saving a document, which itself has only one reference, causes ALL
the references of NodeX to be updated/saved?



On 9/12/06, Christoph Kiehl <kiehl@subshell.com> wrote:
>
> 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.
> "published")
>
> 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.
>
> Cheers,
> Christoph
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message