Great, I'll look at this, thank you Lawrence.


Floriane


De : firedrake-bounces@imperial.ac.uk <firedrake-bounces@imperial.ac.uk> de la part de Lawrence Mitchell <lawrence.mitchell@imperial.ac.uk>
Envoyé : jeudi 19 octobre 2017 10:43:04
À : firedrake@imperial.ac.uk
Objet : Re: [firedrake] Profiling
 


On 19/10/17 10:35, Floriane Gidel [RPG] wrote:
> Dear all,
>
>
> How can I profile my firedrake script to known the allocation of the
> computational time?
>
> I tried 
>
> python -m cProfile -o output.out my_script.py
>
>
> but the output file is not as expected (part of it is pasted below).

This profile is a binary file which you can analyse in various ways.
Here is a nice introduction:

https://julien.danjou.info/blog/2015/guide-to-python-profiling-cprofile-concrete-case-carbonara

In addition to this, a high level view of the time breakdown can be
obtained by running:

python my_script.py -log_view

This prints a summary of the timings for all the PETSc calls and the
main (computationally expensive firedrake calls).  If you send this,
we can help to look at it.  Chapter 13 of the PETSc manual
(http://www.mcs.anl.gov/petsc/petsc-current/docs/manual.pdf) also
gives good information on how to interpret this data.

Cheers,

Lawrence

_______________________________________________
firedrake mailing list
firedrake@imperial.ac.uk
https://mailman.ic.ac.uk/mailman/listinfo/firedrake