jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra" <tobias.bocane...@day.com>
Subject Re: importXML() fails with a ConstraintViolationException
Date Wed, 28 May 2008 10:19:33 GMT
On 5/28/08, Stefan Guggisberg <stefan.guggisberg@day.com> wrote:
> On Wed, May 28, 2008 at 10:13 AM, Alexander Klimetschek
>  <aklimets@day.com> wrote:
>
> > Hi Frederic,
>  >
>  > in general using import/export XML (especially for larger XML chunks)
>  > is not the most efficient way to work with JCR. Using the API directly
>  > in combination with an effective content model is the way to go. An
>  > effective content model tries to reduce the number of nodes (XML
>  > imports tend to create lots of nodes with a single property at the
>  > leaf) and has a high properties/nodes ratio: something around 10 is
>  > good (ie. 10 times more properties than nodes). This is especially
>  > true if you use a bundle persistence manager (which you should ;-)),
>  > because it reads/writes bundles that consist of a node and all its
>  > properties (except for larger binary properties that will go into the
>  > DataStore, if configured).
>  >
>  > Having flat hierarchies ("repository in width") is not efficient,
>  > since Jackrabbit has a limitation when you have many child nodes (>
>  > 1000) under one node
>
>
> i don't know how you determined that limit but it's IMO rather defensive.
>  tests that i've run a while ago showed that there's no significant
>  performance impact with up to 10k child nodes (which is quite a lot).
ok then :-) keep it below 10k :-)

--
toby

Mime
View raw message