jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Laurent Belmonte <laurent.belmo...@gmail.com>
Subject Re: Performance bottleneck
Date Wed, 18 Jan 2006 13:40:33 GMT
On 1/18/06, Stefan Guggisberg <stefan.guggisberg@gmail.com> wrote:
> hi laurent,

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

My test is very simple :
for(i=0; i < 20000; i++ ) {

   .. setting 3 properties..

   session.save(); called every 1000 nodes created

When a child is created, pm store(NodeState) is called. Each time a
node is stored in DerbyStore, the enterily list of his childs is
re-written and more there is children more this operation take time (
the same fact is true for xmlpm and objectpm).

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

maybe, maybe not. Image an application which manage contacts. Maybe a
user of this application wouild want to import all his adressbook in
the application resulting in a node containing 10000 nodes ( yeah he
know lots of people ;) ). This operation can take time because 10000
contacts is a huge amount of data. But after when he will want to add
only one contact, the time of creation will be not acceptable for him.

Best regards,
> cheers
> stefan

View raw message