Problem retrieve studys of Orthanc for receive the OsiriX Dicom VIewer.

rodrigo.n...@medicalharbour.com

unread,

Sep 7, 2016, 5:01:01 PM9/7/16

to Orthanc Users

Hi,

Orthanc with a time log for retrieve images of origin receive for OsiriX DICOM Viewer.

The timeout is retrieve is over two minutes of start is to retrieve.

It's problem happens when the studys comes from origin of Router OsiriX DICOM Viewer.

Someone with this problem too?

Thank you.

att.,

Rodrigo Nascimento

Sébastien Jodogne

unread,

Sep 8, 2016, 3:16:38 AM9/8/16

to Orthanc Users

Hello,

Firstly, make sure you have sufficient knowledge of the DICOM network protocol (especially wrt. query/retrieve):

https://orthanc.chu.ulg.ac.be/book/dicom-guide.html#dicom-network-protocol

Secondly, please carefully follow the troubleshooting guide for DICOM communications, and provide all the required information:

https://orthanc.chu.ulg.ac.be/book/faq/dicom.html

Regards,

Sébastien-

rodrigo.n...@medicalharbour.com

unread,

Sep 17, 2016, 10:21:59 AM9/17/16

to Orthanc Users

I realize that the Orthanc requires more time to retrive studies as the bank becomes more full.

Retriever to start in two to three minutes.

I'm using Orthanc on an estancia in the Amazon Linux Ubuntu dual core processor with 4 memory ram with Postgres Database.

All DICOM parameters were evaluated and not found problems.

It may be a version of Linux problem?

It may be a configuration problem Postgres?

I paste the code of configurate.json?

Thank you.

att.,

Rodrigo Nascimento

Sébastien Jodogne

unread,

Sep 19, 2016, 3:15:46 AM9/19/16

to Orthanc Users

Hello,

I guess your problem is actually a combination of two factors:

(1) You might use a version of Orthanc that was compiled in "Debug" mode, which enables time-consuming run-time debug assertions. A FAQ entry was recently introduced on this topic:

https://orthanc.chu.ulg.ac.be/book/faq/troubleshooting.html#performance-issues

(2) A serious performance issue in C-FIND was fixed a few days ago:

https://groups.google.com/d/msg/orthanc-users/xCfmPIHHUeE/d4hOpGycAgAJ

The fix is currently only part of the mainline version of Orthanc, and will be shipped in forthcoming release 1.1.1.

So, I would suggest you to try again by using the mainline version of Orthanc compiled in "Release" mode.