On Thu, 18 Jul 2013, 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.
I'm definitely not happy with it, but I'm okay with it. We ought to put some warnings in the changelog, though. The RB code is the only example code that allocates additional matrices on top of the ImplicitSystem matrix, right? I'd bet something about that either has a bug or exposes a PETSc bug. > I'd also like to polish off 0.9.2 so we can get on with e.g. > pthreads and other changes. Agreed. --- Roy ------------------------------------------------------------------------------ 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
