jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Guggisberg <stefan.guggisb...@gmail.com>
Subject Re: Performance bottleneck
Date Wed, 18 Jan 2006 13:18:06 GMT
hi laurent,

On 1/18/06, Laurent Belmonte <laurent.belmonte@gmail.com> wrote:
> On 1/18/06, Martin Perez <mpermar@gmail.com> wrote:
> > What persistence manager are you using?
> >
> > It has been commented that XMLPM or ObjectPM are not very good performance
> > persistence managers...
>
> I have done a test with DerbyPM. The results :
> creating 999 nodes on a node already containing 0 childs         take 5402 ms
> creating   1 node  on a node already containing 999 childs       take 126 ms
> creating 999 nodes on a node already containing 1000 childs      take 4292 ms
> creating   1 node  on a node already containing 1999 childs      take 137 ms
> creating 999 nodes on a node already containing 2000 childs      take 3796 ms
> creating   1 node  on a node already containing 2999 childs      take 254 ms
> creating 999 nodes on a node already containing 3000 childs      take 4702 ms
> creating   1 node  on a node already containing 3999 childs      take 370 ms
> .
> .
> .
> creating 999 nodes on a node already containing 20000 childs     take 32841 ms
> creating   1 node  on a node already containing 20999 childs     take 9473 ms
> .
> .
> .
> creating 999 nodes on a node already containing 28000 childs     take 41058 ms
> creating   1 node  on a node already containing 28999 childs     take 19228 ms
>
> as you can see. More a node have childs, more time is taken for create
> one child.
>

this is not a PersistenceManager issue. are you creating same-name sibling
or uniquely named child nodes? what svn rev. are you using?

btw: i would argue that a content model with 30'000 child nodes could probably
be optimized.

cheers
stefan

Mime
View raw message