Performance issues with Bahmni EMR

One of our bahmni implementations have lot of patient and obs data (around 3200000~ obs). Prod System requirements - 23GB, 12 core CPU. We have been facing performance issues for quite sometime. At least once in 45 days openmrs stops responding, restarting openmrs and mysql services used to solve the issue. We have faced this issue with bahmni 0.91. Recently we have upgraded bahmni from 0.91 to 0.92 and we started observing the same issue again. (Even with platform and http upgrade )

Similar issue has reported long back in the bahmni community and below is the JIRA card created in product backlog -

Below are the few points from JIRA card which applicable to our implementation too

  1. Peak times usually the load average touches 11 and CPU has 12 cores and users start complaining of extreme slowness
  2. The memory keeps increasing over a few days until restart

We started debugging issue. We are leveraging the Grafana graphs to analyse the issue. Meanwhile if somebody already noticed/tried to fix it, your points will be much helpful. Thanks !

@ajeenckya @arjun @mksrom @pramidat @ramashish @shivarachakonda @binduak @swetha184 @laxman @anandpatel @snehabagri @sushilp @sushmit @vmalini @akhilmalhotra @dipakthapa @ramashish@pradipta @mddubey @rrameshbtech @mddubey @iadksd @angshuonline @mwelazek @michaelbontyes @buvaneswariarun @praveenad @sanjayap @florianrappl @apaule @mwelazek @som.bhattacharyya @tejakancherla @rabbott @muhima08 @thomasrod @buvaneswariarun @swedhan @kirity @dkayiwa

1 Like

@binduak - for what it’s worth, we had a similar issue with our deployment (using an earlier version of Bahmni) and in our case the issue was related to the allocation of heap space. We had a cluster of errors in /var/log/openmrs.log at times that coincided with slow performance: java.lang.OPutOfMemoryError: Java heap space. We were able to resolve the issue by setting some flags in Tomcat. We did read that the issue was fixed in more recent versions of OpenMRS but I’m not sure of the exact version in which this was resolved