On Oct 30, 2013, at 10:03 AM, Cody Permann <codyperm...@gmail.com> wrote:
> Very interesting, we are all about making sensible default choices for our > users. We might make MOOSE default to sfc_hilbert for meshes built with the > internal generator. At least until we figure out how to make Metis/Parmetis > work better. I can't even come close to getting this problem to run on this > many processors when using Metis right now. I run out of memory at about > 1/8th this number of cores... More investigation will be necessary. Definitely. I wonder if having build_cube() set the SFC partitioner might be a good way to go. Let me know how things compare with an AMR problem, especially with ParallelMesh if you can - Parmetis has a diffusion-based repartitioning scheme that seeks to minimize data movement and could be better than just repartitioning the whole mesh regardless of initial distribution, which is what SFC would do for an adaptive repartitioning. Of course, not allocating that much memory might make it a net speed win! -Ben ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
