topic Re: Optimize JVM memory for AAAR in Alfresco Archive

Optimize JVM memory for AAAR

chooli — Fri, 03 Oct 2014 13:33:52 GMT

I have spent sometime on AAAR installation and customization to make it works for my client's alfresco production. Thanks for the contribution of this great audit report extension. And, kindly help to solve my environment issues.Now the AAAR runs well on a single cloud host server with <strong>

Re: Optimize JVM memory for AAAR

fcorti — Sun, 05 Oct 2014 20:14:02 GMT

Hi Chooli,

Your case it's very interesting and congrats for your job.

Please confirm you run AAAR extraction (so, PDI processes) in a low activity time for Alfresco users.
In my experience the most common scenario is: during the day time the Alfresco resources need to be highly available for performance reasons and during the night time the PDI resources need to give the best performance to the extraction.

If this is true also in your case and you are sure about it, I suggest you to think about increasing the memory for PDI because your value (512Mb) it's quite low.
Of course, during the night time, you would have to think to a strategy to reduce the amount of memory used by tomcat (stop the tomcat? restarting it with a low memory?).

If you are not sure about the hours of activity time on your Alfresco, I suggest you to use the report below.
http://fcorti.com/alfresco-audit-analysis-reporting/aaar-reports-dashboards-extractions/aaar-report-7-activities-day-hours-ecm/

Every comment or contribution is appreciated and, please, let us know how it goes.

Re: Optimize JVM memory for AAAR

chooli — Mon, 06 Oct 2014 13:37:03 GMT

Thanks for your suggestion, Francesco.

I will try to increase PDI memory when do data extraction. The reports now runs well, but it got an issue when user launch the main dashboard at the first time. The error showing on the page is

Error processing component (RepositoryPerDay)
Error processing component (ActionsPerDay)

I grep this error on all source files and logs but just not able to find where it came from. I wonder if this happens due to memory insufficient. Or, if increase memory can solve the problem.

Don't know how to reduce the memory used dynamically at nighttime for tomcat since heap size is set by JAVA_OPT parameter in the environment. Stop and restart might work, but production should runs in 24X7. Technical downtime shouldn't happen regularly.