[vtkusers] Memory problem

[Raúl Ferriz]

El 15/07/2010 17:11, David Gobbi escribió:
> Memory fragmentation is a severe problem on 32-bit windows systems.
> Switching to Win64, Unix, or a Mac will mostly eliminate memory
> fragmentation.
>
> If you are wondering about streaming from disk (i.e. only reading part
> of the volume at a time) it is usually only possible when reading data
> slice-by-slice, so it is not useful for doing MPRs.  So you must have
> at least enough memory to read the whole volume, and for best
> performance you should call Update on the reader to make sure it loads
> the whole volume because streaming from disk is very slow.
>
> To save memory, it is important to put your slice extraction filter
> immediately after the reader.  If you put any other sort of filter
> after the reader, then there is a chance that that filter will operate
> on the whole extent of the image instead of acting on just the slices
> that you are currently viewing.
>
>    David
>
>    

Hi David!

My pipeline looks like:
vtkGDCMImageReader --> vtkImageChangeInformation (to correctly set 
ZSpacing)
Now from this output 
->vtkImageShrink3D->vtkContourFilter->vtkPolyDataMapper->vtkActor
and also the output from vtkImageChangeInformation goes to 3 
vtkImageReader2 (one for each slicer)

Is there a way to optimize this?