Re: Profiling VTK/Performance improvements (with Python)

Some filters can be quite slow indeed.

I played around a bit to compare the performance of a vtkClipDataSet and a
vtkTableBasedClipDataSet to extract an isosurface on an unstructured grid,
and this is what I get:

Total number of cells : 41.16 million.

Using vtkClipDataSet:
 -> Clip Time : 83.096 [s]

Using vtkTableBasedClipDataSet:
 -> Clip Time : 6.173 [s]

Is that a filter you could consider?  They also have some new, fast,
isosurface generators which should parallelize nicely:
https://vtk.org/doc/nightly/html/classvtkFlyingEdges3D.html#details

I haven't worked with them myself, but the claim is that they offer a
significant speed-up. 

I would definitely be interested in hearing if you found a suitable
solution,

Kind regards,
Francois.





--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Users-f1224199.html
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ

Search the list archives at: http://markmail.org/search/?q=vtkusers

Follow this link to subscribe/unsubscribe:
https://vtk.org/mailman/listinfo/vtkusers