From: Roy S. <roy...@ic...> - 2013-09-06 20:24:23
|
On Fri, 6 Sep 2013, Manav Bhatia wrote: > -- BoundaryInfo::sync() still calles the MeshSerializer on the parent mesh. Considering that this is a bottleneck that > I am trying to get away from, is this something that can somehow be circumvented? It's something that circumvents itself. Investigate that MeshSerializer creation more closely: the interior mesh gets serialized *only* if the boundary_mesh object turns out to be impossible to parallelize. Use ParallelMesh for both objects and no serialization is done and none is necessary. > -- Is it possible to create a BoundaryMesh and then call the MeshSerializer on it? It should be possible. However here I mean "should" in the normative sense of "if it doesn't work, that's a bug we need to fix", though, *not* in the positive sense of "I've tested that and expect it to work". --- Roy |