<div>Thank you Barry,<br></div><div>I will check my code for memory leak.</div><div><br></div><div>Sorry for the question. I was not clear enough.</div><div>I was trying to point out Time Ratios for MatView(in the first output) and MatView,MatGetRowIJ (in the second output).</div>
<div>Why are these values huge compared to others?</div><div><br></div><div>Regards,</div><div>Ilyas</div><div><br></div><br><div class="gmail_quote">2011/5/13 Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On May 13, 2011, at 8:56 AM, ilyas ilyas wrote:<br>
<br>
><br>
> Hello,<br>
><br>
> Would you please help me to understand two attached -log_summary outputs. Both are from same cfd-petsc code, taken at different times at the end of first time-step.<br>
><br>
> Domain : 256^3, periodic (defined in DA's)<br>
> Ncores : 256<br>
><br>
> After a couple of hundered iterations, one or more cores killed/dumped and my code exits.This is not an issue with a coarse resolution (say 32^3,64^3) May this be related to my code?<br>
<br>
</div>Object Type Creations Destructions Memory Descendants' Mem.<br>
Reports information only for process 0.<br>
<br>
--- Event Stage 0: Main Stage<br>
<br>
Distributed array 1 0 0 0<br>
Vec 597 579 340156096 0<br>
Vec Scatter 3 1 868 0<br>
Index Set 9 9 1700440 0<br>
<br>
I'm thinking there may be a memory leak with the vectors. During the run you sent us it is creating 597 vectors but only destroying 579. If each time-step you are leaking vectors it will eventually run out of memory and stop. Check that all your Vec creations have a matching destroy. Also make sure that is true for matrices. You can run with the options -malloc -malloc_debug -malloc_dump as a test and it will print out all the memory that PETSc used that was not freed. Ideally this will always report nothing after a run. BTW: Don't use these options when running for performance, just use them to test for memory leaks.<br>
<div class="im"><br>
<br>
> (Assuming enough memory available in the system). What is wrong with MatXXX ?<br>
<br>
</div> Not sure what you mean here? There is no MatXXX in the output you sent us. It is true that since the matrices take up a lot of memory when memory is leaked often it crashes when trying to allocate a matrix.<br>
<br>
Barry<br>
<div class="im"><br>
><br>
> Thanks a lot,<br>
><br>
> Ilyas.<br>
> Energy Inst.<br>
> ITU<br>
</div>> <185432.out><185433.out><br>
<br>
</blockquote></div><br>