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
Describe the bug
Two users encountered an issue when loading fairly high resolution imagery in the web version (from viame.kitware.com instead of a locally hosted version) it periodically only partially loads, and generally a portion of the image (horizontally at the bottom) is black. Sometimes refreshing fixes this or triggers the imagery to stop displaying in certain other parts, other images, or fixes it.
It's unclear if server load has an affect on this (e.g. training jobs writing out a lot of data to disk affecting load times), or other factors like low local bandwidth or firewalls.
The text was updated successfully, but these errors were encountered:
One first thing I can think of is to prevent image sequences with very large images from attempting to cache multiple seconds of the image. Caching attempts to cache 2 seconds before and 1 second behind based on the dataset framerate. In some of the other image-sequences this makes sense but if each image is 10MB and the frame rate is 10fps (as seen in some of these datasets) it is trying to pre-cache 100's of MB of data.
The other option is switching to the new girder WSGI stuff that has been worked on to allow more subsequent requests without the dropping of them.
Describe the bug
Two users encountered an issue when loading fairly high resolution imagery in the web version (from viame.kitware.com instead of a locally hosted version) it periodically only partially loads, and generally a portion of the image (horizontally at the bottom) is black. Sometimes refreshing fixes this or triggers the imagery to stop displaying in certain other parts, other images, or fixes it.
It's unclear if server load has an affect on this (e.g. training jobs writing out a lot of data to disk affecting load times), or other factors like low local bandwidth or firewalls.
The text was updated successfully, but these errors were encountered: