That's right! This is the classic space versus time tradeoff. In the bigger scheme of things, using a little more memory is usually fine on a modern system. The SerialMesh (now called ReplicatedMesh) is quite a bit faster. I think the general consensus is: use ReplicatedMesh until you are truly memory constrained AND you know that the bulk of the memory is in your mesh and not your matrices and vectors and everything else.
Cody On Wed, Jun 8, 2016 at 2:40 PM Xujun Zhao <xzha...@gmail.com> wrote: > Hi all, > > I am curious about SerialMesh running with multiple CPUs. If I have 1 node > with 16 cores on the cluster. Will "mpirun -n 16" lead to 16 copies of > SerialMesh? If so, it looks like running on multiple CPUs will require more > memory?? > > Thanks. > Xujun > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > Libmesh-users mailing list > Libmesh-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libmesh-users > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
