Optimize OpenMRS for Memory Usage on OpenSRP/OpenMRS Instances
Opened this issue · 0 comments
morrismukiri commented
- Manage Scheduler: By default OpenMRS runs two scheduled jobs Auto Close Visits Task and Process HL7 Task which are expensive and we don't currently require/utilize this services.
Stopping or entirely deleting this jobs is recommended - Trim down unused Modules: OpenMRS comes pre-loaded with recommended modules, however for the purpose we use OpenMRS for not all this are required
-Required modules for OpenSRP- ID Generation
- OpenMRS UI Framework
- Address Hierarchy
- Registration Core Module
- Event Module
- Provider Management Module
- Team Management Module
- UI Commons Module
- Rest Web Services OMOD
- Legacy UI Module
- UI Library Module
- Decrease logging for OpenMRS services and OpenMRS tomcat instance: OpenMRS logs most of the services which increases resource usage configuring log levels to high values helps to reduce what is being logged by OpenMRS
- Patient Identifier Type Management: By default OpenMRS comes with OpenMRS ID required while creating a patient, OpenSRP does not provide for this, while setting up OpenMRS this needs to be disabled or marked as not required
- Search Index: rebuild the search index