cancel
Showing results for 
Search instead for 
Did you mean: 

Session.save is slow!

ananius
Champ in-the-making
Champ in-the-making
Hi,

We have been developing project on top of Alfresco and we are accessing it through JCR. But there's a performance problem when storing nodes, which we have profiled more accurately to org.alfresco.jcr.session.SessionImpl.save() -method. It takes several seconds, about 70-80% of the whole transaction.

In the transaction we are saving one node, which has child node hierarchy on few levels (about 20-30 childnodes in all). We have profiled alfresco during this, and most of the time seems to be spent by lucene. Contents of the nodes are quite small and index/atomic is set to false in type definitions so that indexing would happen in background. Slowness seems to correlate more with node count / hierarchy complexity to be stored, than node contents.

Has anybody a clue why this is so slow, and could something be done to it?
1 REPLY 1

paulhh
Champ in-the-making
Champ in-the-making
Hi Antti

Thanks for bringing this to our attention - we haven't seen multi-second delays on save(), but we are aware it is doing a lot of work.  The easiest way to understand what you're seeing is to have a copy of the model you're using and some sample data - we can then investigate.  If that's difficult or undesirable to do over the forum, send it to info at alfresco (we can still continue discussion here).

Cheers
Paul.