MainApp performance is very low. E.g. region grower in interactive segmentation is nearly not useable anymore in release mode. In debug mode it is not useable at all.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Invalid | None | T2317 MITK application is too slow | ||
| Resolved | None | T3829 Surface visualization considerably slows down after changing color |
Event Timeline
Comment Actions
After "researching" what is claimed to be too slow:
(i.e. when MITK is used in Radiology)
- Slicing an Image with Wheel in a 2D Window appears to be slow when also an segmentation (a Surface) is loaded/generated
- Loading Images seems slow
- Interactive Segmentation reacts "laggy"
Comment Actions
Region Growing is almost unusable slow...
An example dataset is:
G:\home\hartmanp\I0000006.vol
Comment Actions
Slicing an Image with Wheel in a 2D Window appears to be slow when also an
segmentation (a Surface) is loaded/generated
-> is fixed, was a global reinit problem
Loading Images seems slow
-> implement streaming load
Comment Actions
Bug is not very specific. My images load in accetpable speed. Can we maybe close this, Markus?
Comment Actions
One reason for the very slow slicing could be that a bounding box is calculated for every slice in order to handle oblique slicing. In most cases (when you slice axis-parallel through an image) this is completly unnecessary. I think this is even done 3 times (because we have 3 render windows) if you slice just through one dimension.
I would like to talk with Markus about this and move it to the T8165. Unfortunately, this does not really make sense until I finished T7027.
Comment Actions
Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.