Enable caching of (static) meshes for transient data
Following on from:
<a rel="nofollow noreferrer" href="http://markmail.org/message/b3ro3hvuqqenxyfg">http://markmail.org/message/b3ro3hvuqqenxyfg</a>
- for transient cases employing static meshes, provide a mechanism to cache the mesh so that it is not necessary to rebuild the complete visualization pipeline
Adminberk.geveci (Admin, paraview) commented
If I understand this request correctly, it is not easy to implement. It would somehow require separating processing related to the mesh from the processing related to the variables. For example, a slice filter does not have to recompute its output geometry but it has to copy the new variables to.
In my experience, the biggest bottleneck with such problems is reloading of the geometry. Would you rather we focus on developing readers that supported static meshes?
Mark Olesen commented
The next bits on the same thread ( http://markmail.org/message/2fpjy7n3qjuymwyz ) look like they would be quite promising.