Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Improve Performance of OHIF renders using DICOMJson as a data source #4582

Open
highoncarbs opened this issue Dec 9, 2024 · 3 comments
Labels
Awaiting Reproduction Can we reproduce the reported bug?

Comments

@highoncarbs
Copy link

Describe the Bug

Right now , we are using OHIF 3.7 using DICOMJson as a datasource, but the loading time is quite slow for large studies.
Is there anything that can be done to speed this up or make it more efficient ? via configs or via parallelizing all the dicom file URLs ?

Steps to Reproduce

use any large DICOMJson data source

The current behavior

The loading time is slow for users

The expected behavior

Make the dicomJson data source faster to render for clients

OS

Windows 11. Edge - Chrom

Node version

20

Browser

Edge, Chrome Latest

@highoncarbs highoncarbs added the Awaiting Reproduction Can we reproduce the reported bug? label Dec 9, 2024
Copy link
Member

sedghi commented Dec 9, 2024

Version 3.7 is outdated, and I don't plan to make further improvements. Please try version 3.9, and if the issue persists, we can address it.

@highoncarbs
Copy link
Author

We also tried with the official OHIf 3.9 deployment - still the same result. Is there anyway to speed this up or make this more efficient

Copy link
Member

sedghi commented Dec 10, 2024

Not really, you can use wado, instead of dicom json https://docs.ohif.org/configuration/dataSources/dicom-web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Reproduction Can we reproduce the reported bug?
Projects
None yet
Development

No branches or pull requests

2 participants