On Sun, 17 Nov 2013, Ataollah Mesgarnejad wrote: > I'm just trying to cut out unnecessary parts of my Code. My main problem is > the memory with my 3-D elasticity + fracture > problem. ParallelMesh helps quite a bit but I would like to make the memory > footprint even smaller and hopefully make things > run a bit faster in the process. I would appreciate any suggestions.
If you're already using ParallelMesh then your next big memory hog is probably the sparse matrix, which suggests one drastic option: switch to a Jacobian-free solve. IIRC we've got support for PETSc "shell matrix" interfaces, so you can implement a Jacobian-vector-product function instead of allocating a matrix. --- Roy ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
