Voir la source de HowTo: Profiling LMDZ

== Profiling with gprof ===

The legacy way to profile the model is using <code>gprof</code>.
* ''Pros:'' available everywhere, easy to use
* ''Cons:'' old, bad handling of multithreaded applications, requires instrumentation

<code>gprof</code> is a rudimentary but simple to use tool to profile a sequential executable.

==== Instrumenting the code ====

In the <code>.fcm</code> arch file used, add <code>-pg</code> to <code>BASE_FFLAGS</code> and <code>BASE_LD</code>. Recompile the model.

==== Collecting statistics ====

Run the executable <code>gcm.e</code>. This will generate a <code>gmon.out</code> file locally.

==== Reading results ====

Run <code>gprof gcm.e gmon.out > profiling.txt</code> to get a textual view of the profiling.

For a graphical representation, we recommend using [https://github.com/jrfonseca/gprof2dot gprof2dot], via <code>gprof gcm.e | gprof2dot | dot -Tpng -o output.png</code>. A typical example is shown below.

[[Fichier:gprof.png|400px]]

== Profiling with gprofng ==

== Profiling with scorep & scalasca ==

[[Category:HowTo]]