How to determine the optimal DicomThreadsCount setting value

Hello everyone. I have a question about the meaning of the DicomThreadsCount setting. There is a server with the following characteristics:

  • Intel(R) Xeon(R) CPU-E5-2660 v4 2.00GHz processor, 18 cores, 1 thread per core
  • 64 GB OF RAM
    DicomThreadsCount currently has a value of 16. The load on the server, judging by the Zabbix monitor, is not high. Using the Python plugin, the DICOM instances received simultaneously were measured, and the value was 11 instances per second. Is it possible to increase the DicomThreadsCount value (how to calculate it correctly based on the server parameters?) and will this affect Orthanc’s performance?
1 Like

Hi,

The DicomThreadsCount configuration actually defines the number of concurrent DICOM connection the DICOM server is able to handle at a given time.

So you very likely do not need a high value for this configuration unless you have 20 modalities pushing data at the same time.

The ingest speed is mainly driven by the HDD performance and by DB performance - not really by the CPU. It is also driven by the sender speed ;-).

In the latest Orthanc version, Orthanc shall display HDD bandwidth when reading/writing files from/to disk and should also display the DB latency at startup. That might help identify some bottlenecks.

HTH,

Alain.

2 Likes

Hi,
Thank you very much.
I have about 70 modalities that can simultaneously send research at certain points in time.
As the number of modalities increases, the time to send (CStore) research increases, which is why some modalities, such as eFilm, go into timeout.

HTH,

Artem.