Hi,
before I do the update, when I issue a simple C-Find query like this:
~/dcm4che-2.0.28/bin/dcmqr -I ORTHANC@localhost:4242 -r 00100020 -qStudyInstanceUID=""
it will take like 100-200ms, now after the update (and I updated db as prompted when I first launched orthanc), the same query will take 28 seconds to complete:
18:27:59,793 INFO - Received 5 matching entries in 28.682 s
is there some extra configuration or db specific config I missed?
thanks.
P.S. It can return the sequence tag now.
Hello,
Your issue is most probably the following, and reflects a performance problem in DCMTK:
https://lists.debian.org/debian-med/2015/05/msg00110.html
You should try and statically link Orthanc against DCMTK. Statically linking against DCMTK will automatically apply the patch enclosed with the message above.
To do so, when invoking cmake, add the “-DUSE_SYSTEM_DCMTK=OFF” option.
HTH,
Sébastien-
Thanks for reply!
I did a fresh build, erased everything, and statically linked dcmtk, but c-find is still very slow.(c-store is fast though). Also the dicom-web error is gone now.
Should I not to use the system boost also?
Hello,
I cannot reproduce your performance issue. Here is an excerpt from my own debugging session:
jodogne@localhost:~/Downloads/dcm4che-2.0.29/bin$ ./dcmqr -L ORTHANCTEST -I ORTHANC@localhost:4242 -r 00100020 -qStudyInstanceUID=“”
12:15:43,423 INFO - Association(1) initiated Socket[addr=localhost/127.0.0.1,port=4242,localport=55434]
12:15:43,424 INFO - ORTHANC(1): A-ASSOCIATE-RQ ORTHANC << ORTHANCTEST
12:15:43,427 INFO - ORTHANC(1): A-ASSOCIATE-AC ORTHANCTEST >> ORTHANC
12:15:43,428 INFO - Connected to ORTHANC@localhost:4242 in 0.024 s
12:15:43,474 INFO - Send Query Request using 1.2.840.10008.5.1.4.1.2.2.1/Study Root Query/Retrieve Information Model - FIND:
(0008,0052) CS #6 [STUDY] Query/Retrieve Level
(0010,0020) LO #0 [] Patient ID
(0020,000D) UI #0 [] Study Instance UID
[…]
12:15:43,483 INFO - Query Response #1:
(0008,0052) CS #6 [STUDY] Query/Retrieve Level
(0010,0020) LO #8 [xxxxxx] Patient ID
(0020,000D) UI #44 [1.3.51.0.1.1.192.168.29.133.1681753.1681732] Study Instance UID
[…]
12:15:43,800 INFO - Query Response #23 for Query Request #4/4:
(0008,0016) UI #26 [1.2.840.10008.5.1.4.1.1.4] SOP Class UID
(0008,0018) UI #52 [1.3.12.2.1107.5.2.33.37097.2012042312584363994737278] SOP Instance UID
(0008,0052) CS #6 [IMAGE] Query/Retrieve Level
(0010,0020) LO #8 [xxxxxx] Patient ID
(0020,000D) UI #44 [1.3.51.0.1.1.192.168.29.133.1688840.1688819] Study Instance UID
(0020,000E) UI #58 [1.3.12.2.1107.5.2.33.37097.2012042312581480428237184.0.0.0] Series Instance UID
(0020,0013) IS #2 [23] Instance Number
12:15:43,800 INFO - Received 92 matching entries in 0.373 s
12:15:43,800 INFO - ORTHANC(1) << A-RELEASE-RQ
12:15:43,801 INFO - ORTHANC(1) >> A-RELEASE-RP
12:15:43,801 INFO - Released connection to ORTHANC@localhost:4242
12:15:43,801 INFO - ORTHANC(1): close Socket[addr=localhost/127.0.0.1,port=4242,localport=55434]
So, I receive 92 matches in third of a second. This looks like a problem that is local to your installation. I cannot provide any further help…
Sébastien-