Sorry, hit the wrong button.
On Fri, Dec 21, 2018 at 7:56 PM Fande Kong wrote:
>
>
> On Fri, Dec 21, 2018 at 9:44 AM Mark Adams wrote:
>
>> Also, you mentioned that you are using 10 levels. This is very strange
>> with GAMG. You can run with -info and grep on GAMG to see the sizes and the
>>
Thanks so much, Hong,
If any new finding, please let me know.
On Fri, Dec 21, 2018 at 9:36 AM Zhang, Hong wrote:
> Fande:
> I will explore it and get back to you.
> Does anyone know how to profile memory usage?
>
We are using gperftools
The attached simple test program (when compiled in debug mode with gfortran and
mpich) throws a lot of valgrind errors on the call to PetscViewerAsciiOpen, as
well as the call to MPI_Comm_split.
I can’t figure out if it is a problem in the code, or a bug somewhere else.
Any advice is
On Fri, Dec 21, 2018 at 12:55 PM Zhang, Hong wrote:
> Matt:
>
>> Does anyone know how to profile memory usage?
>>>
>>
>> The best serial way is to use Massif, which is part of valgrind. I think
>> it might work in parallel if you
>> only look at one process at a time.
>>
>
> Can you give an
Matt:
Does anyone know how to profile memory usage?
The best serial way is to use Massif, which is part of valgrind. I think it
might work in parallel if you
only look at one process at a time.
Can you give an example of using Massif?
For example, how to use it on
On Fri, Dec 21, 2018 at 11:36 AM Zhang, Hong via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> Fande:
> I will explore it and get back to you.
> Does anyone know how to profile memory usage?
>
The best serial way is to use Massif, which is part of valgrind. I think it
might work in parallel if
Also, you mentioned that you are using 10 levels. This is very strange with
GAMG. You can run with -info and grep on GAMG to see the sizes and the
number of non-zeros per level. You should coarsen at a rate of about 2^D to
3^D with GAMG (with 10 levels this would imply a very large fine grid
Fande:
I will explore it and get back to you.
Does anyone know how to profile memory usage?
Hong
Thanks, Hong,
I just briefly went through the code. I was wondering if it is possible to
destroy "c->ptap" (that caches a lot of intermediate data) to release the
memory after the coarse matrix is
