Just to add something to this - we've been seeing a memory "leak" associated with m├ętis during adaptive simulations in parallel... every time it repartitions it doesn't seem like we get all the memory back.

I don't remember if we ran that through valgrind yet or not.  It may not actually "leak" but it might accumulate over time...


Sent from my iPhone

On Oct 29, 2013, at 6:01 PM, John Peterson <jwpeterson@gmail.com> wrote:

On Tue, Oct 29, 2013 at 4:08 PM, John Peterson <jwpeterson@gmail.com> wrote: 

Ben, it looks like we currently base our partitioning algorithm choice solely on the number of partitions...  Do you recall if PartGraphKway is any more memory efficient than the PartGraphRecursive algorithm?  If so, perhaps we could base our algorithm choice on the size of the mesh requested as well as the number of partitions... I might experiment with this a bit as well.

Testing the PartGraphKway algorithm now, will report back with results...

Memory usage for PartGraphKway is basically identical to that for PartGraphRecursive.

I guess it makes sense if we are allocating most of the memory up front ourselves and not much is actually being allocated by Metis itself...

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.
Libmesh-devel mailing list