Start here if you are finding your OpenMRS v3 system (aka O3, 3.x) is slower than expected. For instance, if you are finding that the OpenMRS User Interface is slow to load, this list will help you troubleshoot.

If after checking all these things you still have performance challenges: Please let us know! Post some information about your challenges on the OpenMRS Community Forum at https://talk.openmrs.org and please use the Performance Problem Reporting Template at the end of this document to help our community understand your situation.

Check your Version of OpenMRS ESM-Core.

Very early adopters of OpenMRS v3 (O3) may still be on esm-core v4. Version 5 of esm-core includes substantial performance improvements (e.g. over 3x faster loading speed). More information and a migration guide is available here: https://o3-docs.openmrs.org/docs/migrate-to-core-v5.en-US#introduction

Tip: To check the versions of Frontend and Backend Modules you are running in your OpenMRS system, you or your Administrator can use the Implementer Tools to check the version numbers. This list shows the frontend modules introduced by esm-core. In the screenshot below, you can see that this system is using esm-core v5, because esm-primary-navigation app is one of the esm-core modules.

Open

Example of using the O3 Implementer Tools to check module version numbers.

Check your Internet or Intranet Connection

Open

An example of the Chrome Speed Test running in the Chrome browser.

If your implementation is not just deployed on a single local machine, then sometimes slowness is caused by your network speeds. You can easily check your browser speeds by using tools like Chrome’s Internet Speed Test.

Check your Hyperlink Redirect

Some distributions find that the landing page seems to get stuck infinitely loading. If this is your problem, confirm that your landing page hyperlink has been set up as-expected. This is usually defined at the distro level as an Ngnix configuration: see example here.

Example Scenarios:

• If a user is already logged in, o3.openmrs.org is set to auto-route to https://o3.openmrs.org/openmrs/spa/home

• One distribution was only set to auto route to: yourdistro.com/openmrs/spa when it should have been to yourdistro.com/spa/dashboard/home.

Check your Device Specifications.

Sometimes the problem is the hardware itself. If there is a specific type or model of device struggling in your implementations, go to the Device Settings → System Information and take note of the following:

• Device Type: Desktop/Laptop/Tablet (if Tablet, please include screen size, e.g. 8”)

• Operating System and Version Number: ________

• Processor: ____

• Installed Memory (RAM): _____ Available Memory: ____

• Hard Disk Size: _____

Compare this to the Minimum Hardware Specifications for OpenMRS 3.

Performance Problem Reporting Template

If after checking all these things you still have performance challenges: Please let us know! Post some information about your challenges on the OpenMRS Community Forum at https://talk.openmrs.org and please use the Performance Problem Reporting Template below to help our community understand your situation.