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"
On Tue, Oct 29, 2013 at 4:08 PM, John Peterson 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
Thanks, John. I've had limited access today by hopefully can get caught up and
contribute something tonight/tomorrow.
-Ben
On Oct 29, 2013, at 5:09 PM, "John Peterson" wrote:
> On Tue, Oct 29, 2013 at 2:48 PM, John Peterson wrote:
>
>>
>> I just checked out the hash immediately prior to
On Tue, Oct 29, 2013 at 2:48 PM, John Peterson wrote:
>
> I just checked out the hash immediately prior to the latest Metis/Parmetis
> refresh (git co 5771c42933), ran the same tests again, and got basically
> the same results on the 200^3 case.
>
> So I don't think the metis/parmetis refresh int
On Tue, Oct 29, 2013 at 12:31 PM, John Peterson wrote:
>
>
>
> On Tue, Oct 29, 2013 at 11:19 AM, John Peterson wrote:
>
>> On Tue, Oct 29, 2013 at 9:32 AM, Cody Permann wrote:
>>
>>>
>>> On Tue, Oct 29, 2013 at 5:54 AM, ernestol wrote:
>>>
>>> > I am using an cluster with 23 node for a total of 1
On Tue, Oct 29, 2013 at 11:19 AM, John Peterson wrote:
> On Tue, Oct 29, 2013 at 9:32 AM, Cody Permann wrote:
>
>>
>> On Tue, Oct 29, 2013 at 5:54 AM, ernestol wrote:
>>
>> > I am using an cluster with 23 node for a total of 184 cores, and each
>> node
>> > additionally has 16GB of RAM. I was thi
Could you manually use the space filling curve partitioner (hard code?) to see
if that is better behaved?
On Oct 29, 2013, at 12:19 PM, "John Peterson" wrote:
> On Tue, Oct 29, 2013 at 9:32 AM, Cody Permann wrote:
>
>>
>> On Tue, Oct 29, 2013 at 5:54 AM, ernestol wrote:
>>
>>> I am using a
On Tue, Oct 29, 2013 at 9:32 AM, Cody Permann wrote:
>
> On Tue, Oct 29, 2013 at 5:54 AM, ernestol wrote:
>
> > I am using an cluster with 23 node for a total of 184 cores, and each
> node
> > additionally has 16GB of RAM. I was thinking that the problem maybe is in
> > the code. Because if I ru
Copying to libmesh-users
-- Forwarded message --
From: Cody Permann
Date: Tue, Oct 29, 2013 at 9:32 AM
Subject: Re: [Libmesh-users] Memory usage in 3D mesh generation
To: ernestol
libMesh doesn't generate meshes "in parallel", or to be more specific, it
doesn't spread the work
