Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: After session.save() takes 15 minutes for 6K nodes
Date: Tue, 10 Jun 2008 12:24:31 -0500
Message-ID: 
 <01E8A990E317A1409EEC9E6858B09B9501B81111@USDALSMBS02.ad3.ad.alcatel.com>
In-Reply-To: 
 <01E8A990E317A1409EEC9E6858B09B9501B12183@USDALSMBS02.ad3.ad.alcatel.com>
Thread-Topic: After session.save() takes 15 minutes for 6K nodes
Thread-Index: AcjKSKT1vjIzkPYeRhS/mAvjEX4N/AAUKyYgACFMyzA=
From: "MARTINEZ Antonio" <Antonio.Martinez@alcatel-lucent.com>
To: <users@jackrabbit.apache.org>

Hello,

Any idea why it would be slower using the tree structure?=20

Thank you,
Antonio=20

-----Original Message-----
From: MARTINEZ Antonio [mailto:Antonio.Martinez@alcatel-lucent.com]=20
Sent: Monday, June 09, 2008 7:33 PM
To: users@jackrabbit.apache.org
Subject: RE: After session.save() takes 15 minutes for 6K nodes

Hi Stefan,

Thanks for doing that testing.

I have done now two different tests with a scaled down tree (140 Nodes
with about 15 string of 15 bytes each) My server is a SunBlade 1500 with
2G.

- If I build the tree and then save it, it takes about 40 seconds to
save and exit the transaction.

- However, if I just create one node and then add all other nodes as
children of this one (flat storage), then it takes 3 seconds to save and
exit the transaction.

In the tree configuration, most of the nodes are at the deepest level
(there are 10 levels in my case)


I do not understand what is going on

Thanks,
Antonio


-----Original Message-----
From: stefan.guggisberg@gmail.com [mailto:stefan.guggisberg@gmail.com]
On Behalf Of Stefan Guggisberg
Sent: Monday, June 09, 2008 8:50 AM
To: users@jackrabbit.apache.org
Subject: Re: After session.save() takes 15 minutes for 6K nodes

hi antonio

On Mon, Jun 9, 2008 at 5:36 PM, MARTINEZ Antonio
<Antonio.Martinez@alcatel-lucent.com> wrote:
> Hello,
>
> I'm using JackRabbit 1.4.4 with MySql bundle. The string are very=20
> small, I would say 10 bytes average and some strings are 30 bytes. So=20
> I'm not sure DataStore would be of any benefit.
>
> Is there something else that can be done to improve the saving time ?
> Did anybody else have a similar issue?

i ran a quick test on my local machine (2 ghz macbook pro) with mysql
5.0 running on the same machine and using bundle mysql pm;

adding 6k child nodes with 15 string properties of 100 chars each takes
~2 seconds, saving them takes ~44 seconds. i ran jackrabbit
strand-alone, i.e. w/o tx.

maybe you're experiencing a high network latency?

cheers
stefan

>
> Many thanks,
> Antonio
>
>
>
> -----Original Message-----
> From: Alexander Klimetschek [mailto:aklimets@day.com]
> Sent: Sunday, June 08, 2008 11:00 PM
> To: users@jackrabbit.apache.org
> Subject: Re: After session.save() takes 15 minutes for 6K nodes
>
> On Fri, Jun 6, 2008 at 9:13 PM, MARTINEZ Antonio=20
> <Antonio.Martinez@alcatel-lucent.com> wrote:
>> I have an issue saving 6K inside a transaction on Jboss. I have about

>> 6K Nodes in the tree with about 15 String properties each.
>
> How long are the Strings (average and maximum)? If you have long=20
> strings, consider using the DataStore (since Jackrabbit 1.4, see here=20
> http://wiki.apache.org/jackrabbit/DataStore).
>
> Are you using a bundle persistence manager? Which version of=20
> Jackrabbit do you use?
>
> Regards,
> Alex
>
> --
> Alexander Klimetschek
> alexander.klimetschek@day.com
>