Dear list,
I observed a strange behavior of MITK while rendering a lot of images.
First, I have an image that is 3200x2448 pixels large. Also the image is
divided in ~480 tiles. Each tile has a size of 128x128 pixels. Calculating the
size I get ~48kB of raw data per tile. That's 22,4MB of raw data per image
using RGB values. Now if I try to just load a portion of the tiles into MITK,
the memory that MITK utilizes is exploding as soon as MITK renders the images.
I tested this using just image 3 rows with 19 tiles each => 57 tiles total. The
memory requirement of MITK while rendering the images is 940MB. However If I
select a second, preloaded image and don't initialize the render view after
loading the tiles, I just get a total MITK memory usage of 350MB. Starting MITK
had a memory size of 273MB. Further, selecting 6x19 tiles I would have expected
something like 1,8GB with the expensive rendering. But I received a value of
2,5GB MITK memory used. That's nearly triple for twice the images. At which
point I wonder WTF is using all that memory for a 23MB image??
I guess you don't usually load that many tiny images to MITK but I can't
explain this due to OOP overhead.
Best regards,
Matthias
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
