On 07/18/2013 11:54 AM, Kirk, Benjamin (JSC-EG311) wrote: > On Jul 4, 2013, at 8:15 AM, David Knezevic <dkneze...@seas.harvard.edu> wrote: > >>> The reason I ask is that we've identified what I believe to be a bug >>> with Petsc block matrices where they are not honoring >>> KEEP_NONZERO_PATTERN. This is causing a ton of mallocs for us in >>> MOOSE. So, for now, we're just disabling block matrix support in >>> libmesh until we get some clarity on the issue... >> OK, interesting. Disabling block matrix support (using Ben's hard-coding >> suggestion) fixed the mallocs for me as well, so sounds like I might >> have been running into the same issue. > Do we have a consensus path forward here for 0.9.2? I am OK leaving the > '-mat_new_nonzero_allocation_err false' option in the two RB examples that > trigger the issue if everyone else is.
The issue for me is that this also arises in a lot of application codes that me and my colleagues use. We can't use '-mat_new_nonzero_allocation_err false' for larger scale problems since it runs very slowly (presumably due to the mallocs). Is there a configure option for turning off blocked dofs? If so, I can just go ahead and use that (a bit cleaner than hard-coding block size to 1). David ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
