Relevant factors for JCR transaction size

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

996

Correct Reply

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

996

Correct Reply

1.0K
Jörg_Hoh
Employee

05-09-2017

Hi community,

I wrote an article on my blog, where I explain the relevant factors, when it comes to the question "how often should I call session.save()?". The rule of thumb was always "do a save after 1000 nodes", but this might be already too high. Check this article and learn how you can estimate the size on your own:

AEM transaction size or “do a save every 1000 nodes” | Things on a content management system

Jörg

Replies

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

05-09-2017

Excellent community write up.

Avatar

Avatar

Diego_Fontan

Avatar

Diego_Fontan

Diego_Fontan

07-09-2017

Thanks for share.

Avatar

Avatar

RMGJID

Avatar

RMGJID

RMGJID

09-09-2017

This is too good. Thanks for the share!

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.8K

Likes

1.0K

Correct Reply

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.8K

Likes

1.0K

Correct Reply

1.1K
kautuk_sahni
Community Manager

10-09-2017

Thanks for sharing such a nice information with the community.

Let’s conclude: The rule of thumb “do a save every 1000 nodes” might be a bit too optimistic on AEM 6.2 and older (with default values), but ok on AEM 6.3. But always keep the amount of transient space in mind. It can overflow your heap and to debug out-of-memory situations is not nice.

Sums up very nicely.

~kautuk

Avatar

Avatar

sarahjohan

Avatar

sarahjohan

sarahjohan

16-09-2017

Thanks for the Share.