[vtk-developers] vtkGPUInfo and large amounts of memory

[David Gobbi]

On Mon, Jul 7, 2014 at 2:01 PM, Berk Geveci <berk.geveci at kitware.com> wrote:

> My main issue with the current vtkIdType usage is that it is also used
> to define the size of the integer used in cell arrays to refer to points. So
> even if you have less than 2^31 point, you end up using 64 bits in the cell
> array to store the ids. Which doubles the storage. In my opinion, this should
> be run-time configurable. Furthermore, we should use size_t when defining
> offsets into these arrays, not vtkIdType. (See the Locations data member
> of vtkUnstructuredGrid for example).

If it is made to be configurable, I would vote to switch many of the core
VTK filters to templated execute methods (templated over float vs. double
and 64-bit IDs vs. 32-bit IDs).  This would avoid the performance hit of
accessing all points and point IDs through virtual methods.

 - Yet another David (sorry 'bout that...)