On May 28, 2013, at 3:53 PM, Roy Stogner <[email protected]> wrote:
>> >> I have noticed that each time we call solve on a system SNES, KSP, >> PC needed to solve the system are created and destroyed. I was >> wondering what is the reason for creation and destruction of these >> objects per each solve and if there is a way to make the systems use >> the same for example ksp solver over and over. > > I vaguely recall noticing the same thing and assuming the reason was > just "nobody noticed a performance penalty so nobody bothered to fix > it". Unless someone has a better reason we'd probably be happy to > accept a patch. That is pretty much the size of it. Also, the current implementation sort-of assumes adaptivity and makes it easier. If we keep the solvers around we need to delete them before refinement so that we don't exhaust memory for problems that work now. This means the refinement code will need to know something about the solvers... -Ben ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
