On May 30, 2013, at 4:44 PM, "Manav Bhatia" wrote:
> At this stage, should I attempt to read the .xdr file into my code with a
> ParallelMesh data structure? Would the mesh from this .xdr file be read in
> parallel, thereby reducing the memory footprint?
That is the theory. The Xdr io code wil
On Thu, May 30, 2013 at 5:09 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
>
> ExodusII is a serial format, and the reader is serial too I think.
> ExodusII meshes can be pre-partitioned, however, and the pieces read in
> parallel.
>
> I helped put the capability in a few year
On May 30, 2013, at 3:47 PM, Manav Bhatia wrote:
> Hi,
>
> I am attempting to do analysis on a mesh with 8M cells. The mesh was
> created with gridgen, and am using the ExodusII IO class to read the
> mesh. I am using the ParallelMesh class with the library configured with
> Parmetis (and also
Hi,
I am attempting to do analysis on a mesh with 8M cells. The mesh was
created with gridgen, and am using the ExodusII IO class to read the
mesh. I am using the ParallelMesh class with the library configured with
Parmetis (and also with Metis, but I am not sure if this would matter).
The
On Thu, May 30, 2013 at 9:57 AM, Jed Brown wrote:
> Cody Permann writes:
>
> > Yeah, I guess I need to spend more time with Massif. I tried it last
> week
> > for the first time as well and was overwhelmed by the amount of output.
> > From what I've seen just scanning over the output is a deta
Cody Permann writes:
> Yeah, I guess I need to spend more time with Massif. I tried it last week
> for the first time as well and was overwhelmed by the amount of output.
> From what I've seen just scanning over the output is a detailed log of
> when and how much memory is used. Is there a way
On Thu, May 30, 2013 at 10:58 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
>
> This is basically what I do, but I use valgrind's massif tool:
> http://valgrind.org/docs/manual/ms-manual.html
>
> This wraps malloc and reports exactly what memory is used by what data
> structure
Yeah, I guess I need to spend more time with Massif. I tried it last week
for the first time as well and was overwhelmed by the amount of output.
From what I've seen just scanning over the output is a detailed log of
when and how much memory is used. Is there a way to flip that tree
upside-down
Here is a sample of what massif can provide:
#---
snapshot=76
#---
time=34259946158
mem_heap_B=81869326
mem_heap_extra_B=2917770
mem_stacks_B=0
heap_tree=detailed
n7: 81869326 (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
n3: 31253406 0xF0712EE: PetscMallocAlign
On Thu, May 30, 2013 at 7:45 AM, Manav Bhatia wrote:
> Hi,
>
> Is there a way to get the memory footprint of individual datastructures
> in the library? For example, if I want to know the size of a DofMap, and a
> Mesh?
>
> Thanks,
> Manav
>
I'd certainly really like to hear thoughts on this
On May 30, 2013, at 9:32 AM, Cody Permann wrote:
>>
>> Hi,
>>
>>Is there a way to get the memory footprint of individual datastructures
>> in the library? For example, if I want to know the size of a DofMap, and a
>> Mesh?
>>
>> Thanks,
>> Manav
>>
>
> I'd certainly really like to hear
On May 28, 2013, at 11:22 AM, lorenzo alessio botti
wrote:
> Yes you are right, it would be limited to dG, all variables of the same
> polynomial degree and no local P refinement.
> I know that this is very specific but the memory savings are quite
> encouraging.
To properly test for this cas
Hi,
Is there a way to get the memory footprint of individual datastructures
in the library? For example, if I want to know the size of a DofMap, and a
Mesh?
Thanks,
Manav
--
Introducing AppDynamics Lite, a free troubl
13 matches
Mail list logo
