There are lots of possibilities to improve the performance of the new ImageVtkMapper2D:
-The method ComputeClippedPlaneBounds is called everytime. But in most cases we just want to slice paraxial through an image. In this common case the Geoemtry of the 2D slice can be used instead of this method.
-The reslicing (and other things) is performed everytime during the rendering process. Meaning that we reslice the data even if just zoom or color the image. The update method could be optimized with respect to performance.
Because the 2D rendering is performed three times in our rendering pipeline this could increase the performance of MITK significantly.