Difference between revisions of "Gprof Tutorial"
(added another question) |
m |
||
Line 45: | Line 45: | ||
{{hidden begin | {{hidden begin | ||
− | |title = 3. What compiler flag is used to instrument the application? | + | |title = 3. What compiler/linker flag is used to instrument the application? |
}} | }} | ||
<quiz display=simple> | <quiz display=simple> | ||
Line 150: | Line 150: | ||
{{hidden begin | {{hidden begin | ||
− | |title = 9. How much overhead does Gprof produce? | + | |title = 9. How much runtime overhead does Gprof produce? |
}} | }} | ||
<quiz display=simple> | <quiz display=simple> |
Revision as of 15:07, 3 December 2020
This tutorial deals with the topic of applications performance analysis with the GNU profiler Gprof. Profiling applications gives valuable insights into the program structure and exposes performance bottlenecks, which point to sections of the code where optimizations are most effective.
The tutorial covers all necessary basics to get started with Gprof: it shows how to instrument applications, how to generate performance information for an application run and how to evaluate the results. In addition, it explains how to visualize the application structure using call graphs and how to annotate the application's source code with runtime information. Three real-world examples from the areas of biology, computer science and mechanical engineering demonstrate that this works with different programming languages (C/C++, Fortran), different compilers (GNU, Intel) and even parallel applications (threads, MPI).
Quiz