Explorer 2 becomes extremely slow to load the homepage /orthanc/ui/app/

I realised that Orthanc Explorer becomes slow to open when l visit https://mydomain.com/orthanc/ui/app/ and below is what l have observed.

  1. When DICOM files are being received

  2. When we open Meddream Viewer (Using Orthanc Dicom-web setup) and click on preload series to download all the series

My questions are:

  1. Is Orthanc designed to handle multiple dicom C-STORE (20 Modalities sending DICOM files at the same time)? And why does it slow down the loading of the orthanc explorer 2 homepage?
  2. Does the Orthanc Explorer page (list of studies) support pagination?
  3. Any suggestions to optimize the loading of the page when DICOM files are being received? Any configuration settings to consider?

Hi,

  1. Yes / Because it might be busy receiving instances.

  2. no. It is designed to use the search fields. Users should refine their search criteria if there are too many results.

  3. check these settings in OE2 configuration to encourage users to use searches instead of browsing latest studies:

            "StudyListSearchMode": "search-buttontype",// mode to trigger a search in the StudyList.  Accepted values: 'search-as-you-type' or 'search-button'
            "StudyListContentIfNoSearch": "empty", // Defines what to show if no search criteria has been entered
                                                   // Allowed values: "empty", "most-recents"

Also check all issues related to scalability.

HTH,

Alain

@alainmazy Thanks a lot. Your point number 3 has really helped a lot. Also a quick question, would it advisable to have two docker containers running two orthanc servers. One for port 3030 (receiving dicom) and one for accessing port 8042 (explorer 2)? I suspect this will further help with explorer 2 to load faster

Yes, that’s a valid architecture.

However, I’m afraid that won’t help much wrt performance since the bottleneck is very likely the DB and/or the disk IO…

Note that I’m currently working on the DB bottleneck at ingest time.

Thanks a lot. Will be looking forward to your DB bottleneck at ingest changes. Thanks for the good work