Performance Issue of ChildAssocImpl.java (DAO?)

[emil]

Hi, authors of Alfresco. I'm using Alfresco 1.4 as a CMS engine of a enterprise application. However, a serious performance issue blocks my solution.

I found that it was very slow to create a person in Alfresco when there are hunderds of persons in database. I used some SQL monitoring tool to investigate background SQL calling, and I found the number of SQL calling is linear to the number of person nodes.

I am wondering whether it is the issue of Alfresco design or my configuration. Could you give me some suggestion to make the performance better?

//BR
Emil

[derek]

Hi,

Have you tried a later version of the product?  There were some optimizations in the XPath implementation for 1.4.1 Enterprise. (http://issues.alfresco.com/browse/AR-1114)

Regards

[emil]

Hi, thanks for your reply. I found an item (http://issues.alfresco.com/browse/AR-485) in JIRA whose description is similar as my issue, but it was fixed in revision 1.3.
It's so strange…

[derek]

Hi,

It's not strange.  AR-485 was something that happened all the time in 1.3, i.e. all the children were being populated when one was required - regardless of the mode of access.

Your issue is the AR-1114, which pertains to XPath processing only.  The XPath infrastructure was requesting all children and then sorting through them to find the required match.

Regards

[emil]

Thanks, I did some test and found that it's better than 1.3 in performance.
But it's OK to migrate my 1.3 data to 1.4.1?

//BR
Emil

[derek]

Hi,

Yes.  You should upgrade.  But go for the latest 1.4 i.e. 1.4.4 Enterprise.

Regards