In the attached screenshot the gdb output shows that after a single click in the renderwindow, several threads are started and stopped. This causes a noticable delay while debugging the application.
The system monitor shows, that the cpu is not at its capacity.
Description
Description
Event Timeline
Comment Actions
Most of the threads are started during the render routine of the mitkvtkMapper and in the ExtractSliceFilter.
vtk is using the number of cores as the number of threads to start in its filters, so in my case it starts 12 threads for each vtk operation.
I will analyse if the usage of so many threads in a multicore system is creating an overhead and eventually results in a slower performance.
Comment Actions
Christoph, what is the status of this bug? Do you still work on it? Consider to Set status back to Confirmed or Resolved - WontFix/Invalid.
Comment Actions
I'm not working on this. Status is set back to confirmed, as a remainder that this might be a performance issue for multi-core systems.