You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The query to get a list of instances in a local study in Orthanc Raw is sometimes very slow (10+ minutes) and leads to Timeout errors in the imaging api.
Relevant log output (optional)
No response
What did you expect? (optional)
I would expect the call to /studies/id/instances should return within the HTTP timeout limit.
I've tried:
calling different endpoints (e.g. /studies/series to get a list of series in the study and then /series/instances to get the instances in a series, but the call to /series/instances is very slow if there are a large number of instances in the series)
specifying only the SOPInstanceUID tag should be returned in the call to /study/id/instances (although all MainDicomTags are still returned)
making the call to /studies/id/instances synchronously
but none of these to solve the issue. We should perhaps use the DICOM timeout in this api call so we at least don't run into the timeout issues.
The text was updated successfully, but these errors were encountered:
What happened?
The query to get a list of instances in a local study in Orthanc Raw is sometimes very slow (10+ minutes) and leads to
Timeout
errors in the imaging api.Relevant log output (optional)
No response
What did you expect? (optional)
I would expect the call to
/studies/id/instances
should return within the HTTP timeout limit.I've tried:
/studies/series
to get a list of series in the study and then/series/instances
to get the instances in a series, but the call to/series/instances
is very slow if there are a large number of instances in the series)SOPInstanceUID
tag should be returned in the call to/study/id/instances
(although all MainDicomTags are still returned)/studies/id/instances
synchronouslybut none of these to solve the issue. We should perhaps use the DICOM timeout in this api call so we at least don't run into the timeout issues.
The text was updated successfully, but these errors were encountered: