search

OpenImaging / miqa-phase1

A web application for medical imaging quality assurance
MIT License
20 stars 8 forks source link

Investigate performance degradation after scanning through many timesteps #44

Closed scottwittenburg closed 3 years ago

scottwittenburg commented 3 years ago

I have noticed that after scanning through hundreds of timesteps, that the time to move to the next time step slowly grows the more timesteps we view. At first I see a framerate above 10 images/second, but eventually it can take more than a second to move to the next timestep. Reloading the application resets the performance back to expected level.

Use the performance tool in Chrome, it seems the time to switch is partly attributed to vtk.js setting new inputData on the trivial producer which is the source for the visualization, and partly attributed to vue.js re-rendering the DOM. As the timestep switching takes longer and longer, that time becomes dominated by vue.js.

We need to figure out what is causing vue.js to take longer and longer.

This performance degradation is distinct from that we have seen when loading many experiments, and the load time grows over time. However, the two may be related.

scottwittenburg commented 3 years ago

This is related to #43. However, while that is certainly contributing to this degradation in performance, fixing that listener leak may not completely solve this issue.