Gprof Tutorial - Revision history

Christian-siebert-cbc6@uni-duesseldorf.de at 16:48, 3 December 2020

2020-12-03T16:48:53Z

Christian-siebert-cbc6@uni-duesseldorf.de at 14:13, 3 December 2020

2020-12-03T14:13:54Z

Christian-siebert-cbc6@uni-duesseldorf.de: another question

2020-12-03T14:12:25Z

another question

Christian-siebert-cbc6@uni-duesseldorf.de at 14:07, 3 December 2020

2020-12-03T14:07:10Z

Christian-siebert-cbc6@uni-duesseldorf.de: added another question

2020-12-03T13:51:43Z

added another question

Christian-siebert-cbc6@uni-duesseldorf.de: editing of the quiz questions and answers

2020-12-03T13:43:57Z

editing of the quiz questions and answers

Christian-siebert-cbc6@uni-duesseldorf.de: reworked and extended the introduction part

2020-12-03T12:42:44Z

reworked and extended the introduction part

Marc-andre-hermanns-bc32@rwth-aachen.de: Move landing page to MPI-Developer category

2020-11-27T12:47:07Z

Move landing page to MPI-Developer category

Marc-andre-hermanns-bc32@rwth-aachen.de: Remove initial blank lines and infobox to HPC.NRW tutorials

2020-11-20T12:47:54Z

Remove initial blank lines and infobox to HPC.NRW tutorials

Marc-andre-hermanns-bc32@rwth-aachen.de: Marc-andre-hermanns-bc32@rwth-aachen.de moved page GPROF Tutorial to Gprof Tutorial: Adapt to common spelling of Gprof

2020-11-20T12:40:50Z

Marc-andre-hermanns-bc32@rwth-aachen.de moved page Gprof Tutorial to Gprof Tutorial: Adapt to common spelling of Gprof

@@ Line 35: / Line 35: @@
+{
 |type="()"}
-+  By instrumenting the application during compilation.
++ by instrumenting the application during compilation
 || True
--  Through static analysis of the source code
+- through static analysis of the source code
 ||
-- By means of hardware performance counters.
+- by means of hardware performance counters
 ||
 </quiz>
@@ Line 50: / Line 50: @@
+{
 |type="()"}
-+  <code>-pg</code>
++ <code>-pg</code>
 || True
--  <code>-pig</code>
+- <code>-pig</code>
 ||
--  <code>--profile</code>
+- <code>--profile</code>
 ||
 </quiz>
@@ Line 80: / Line 80: @@
+{
 |type="()"}
-- Simple and understandable
+- simple and understandable
 ||
-+ Representative of the usual workload
++ representative of a usual workload
 || True
-- Covering edge cases
+- covering edge cases
 ||
 </quiz>
@@ Line 95: / Line 95: @@
+{
 |type="()"}
-- Only small examples
+- only small examples
 ||
-- Up to medium-sized applications with a running time below ~1 hour
+- up to medium-sized applications with a running time below ~1 hour
 ||
-+ Even large real-world examples with huge running times
++ all, even large real-world examples with huge running times
 || True
 </quiz>
@@ Line 110: / Line 110: @@
+{
 |type="()"}
--  An android app to show incoming callers
+- an android app to show incoming callers
 ||
-+  A hierarchy diagram of function calls in a given profile
++ a hierarchy diagram of function calls in a given profile
 || True
--  Instructions of how to call for help during emergencies
+- instructions of how to call for help during emergencies
 ||
 </quiz>
@@ Line 140: / Line 140: @@
+{
 |type="()"}
-+ Third party script for call graph visualization via the "dot" library
++ third-party script for call graph visualization via the "dot" library
 || True
 - Gprof feature to export profiles as a pdf
 ||
-- A fork of the beta version of Gprof2
+- a fork of the beta version of Gprof2
 ||
 </quiz>
@@ Line 155: / Line 155: @@
+{
 |type="()"}
-- No, Gprof only works with sequential applications
+- no, Gprof only works with sequential applications
 ||
-+ Yes, but Gprof cannot differentiate between individual threads or processes
++ yes, but Gprof cannot differentiate between individual threads or processes
 || True
-- Yes, parallel profiling is the main use-case of Gprof
+- yes, parallel profiling is the main use-case of Gprof
 ||
 </quiz>
@@ Line 170: / Line 170: @@
+{
 |type="()"}
-- None
+- none
 ||
-+ Little
++ little
 || True
-- Much
+- much
 ||
 </quiz>
 {{hidden end}}

@@ Line 60: / Line 60: @@
 {{hidden begin
-|title = 4. Which compiler(s) support(s) Gprof?
+|title = 4. Which compilers support Gprof?
 }}
 <quiz display=simple>
+{
 |type="()"}
-- only commercial compilers (e.g., from Intel)
+- only the commercial Intel compilers
 ||
 - only open-source compilers (e.g., from GNU)

@@ Line 75: / Line 75: @@
 {{hidden begin
-|title = 4. How should the input parameters be when running the instrumented application?
+|title = 5. How should the input parameters be when running the instrumented application?
 }}
 <quiz display=simple>
@@ Line 90: / Line 90: @@
 {{hidden begin
-|title = 5. What is a call graph?
+|title = 6. Which applications can be analyzed with Gprof?
 }}
 <quiz display=simple>
@@ Line 105: / Line 120: @@
 {{hidden begin
-|title = 6. How do you generate a call graph of a Gprof profile?
+|title = 8. How do you generate a call graph of a Gprof profile?
 }}
 <quiz display=simple>
@@ Line 120: / Line 135: @@
 {{hidden begin
-|title = 7. What is gprof2dot?
+|title = 9. What is gprof2dot?
 }}
 <quiz display=simple>
@@ Line 135: / Line 150: @@
 {{hidden begin
-|title = 8. Does Gprof work with parallel applications?
+|title = 10. Does Gprof work with parallel applications?
 }}
 <quiz display=simple>
@@ Line 150: / Line 165: @@
 {{hidden begin
-|title = 9. How much runtime overhead does Gprof produce?
+|title = 11. How much runtime overhead does Gprof produce?
 }}
 <quiz display=simple>

@@ Line 45: / Line 45: @@
 {{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>
@@ Line 150: / Line 150: @@
 {{hidden begin
-|title = 9. How much overhead does Gprof produce?
+|title = 9. How much runtime overhead does Gprof produce?
 }}
 <quiz display=simple>

@@ Line 56: / Line 56: @@
 -  <code>--profile</code>
 ||
 </quiz>
 {{hidden end}}

@@ Line 15: / Line 15: @@
 {{hidden begin
-|title = 1. What lanuages can Gprof profile?
+|title = 1. What languages can Gprof profile?
 }}
 <quiz display=simple>
@@ Line 30: / Line 30: @@
 {{hidden begin
-|title = 2. How does gprof profiles an application?
+|title = 2. How does Gprof generate a performance profile of an application?
 }}
 <quiz display=simple>
@@ Line 38: / Line 38: @@
 || True
 -  Through static analysis of the source code
 ||
 </quiz>
@@ Line 58: / Line 60: @@
 {{hidden begin
-|title = 4. How should the parameters be when running the instrumented application?
+|title = 4. How should the input parameters be when running the instrumented application?
 }}
 <quiz display=simple>
@@ Line 88: / Line 90: @@
 {{hidden begin
-|title = 6. How do you generate a callgraph of a gprof profile?
+|title = 6. How do you generate a call graph of a Gprof profile?
 }}
 <quiz display=simple>
@@ Line 95: / Line 97: @@
 - gprof --call-graph
 ||
-- gprof
+- gprof-call-graph
 ||
 + gprof --graph
@@ Line 112: / Line 114: @@
 - Gprof feature to export profiles as a pdf
 ||
-- A fork of the beta version of gprof2
+- A fork of the beta version of Gprof2
 ||
 </quiz>
@@ Line 118: / Line 120: @@
 {{hidden begin
-|title = 8. Does gprof work with MPI applications?
+|title = 8. Does Gprof work with parallel applications?
 }}
 <quiz display=simple>
+{
 |type="()"}
-- No, gprof only works with sequential applications
+- No, Gprof only works with sequential applications
 ||
-- Yes, parallel profiling is the main use case of gprof
++ Yes, but Gprof cannot differentiate between individual threads or processes
 ||
 </quiz>
 {{hidden end}}
 {{hidden begin
-|title = 9. How much overhead does gprof produce?
+|title = 9. How much overhead does Gprof produce?
 }}
 <quiz display=simple>

@@ Line 2: / Line 2: @@
 [[Category:Tutorials | Gprof Tutorial]]<nowiki />
-Gprof is a free and easy-to-use profiler.
+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.
-This tutorial covers the necessary basics to get started with gprof.
+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).
 __TOC__

← Older revision		Revision as of 12:47, 27 November 2020
Line 1:		Line 1:
−	[[Category:Tutorials]] [[Category:~~Basics~~]]<nowiki />	+	[[Category:Tutorials]] [[Category:HPC-Developer]]<nowiki />
	[[Category:Tutorials \| Gprof Tutorial]]<nowiki />		[[Category:Tutorials \| Gprof Tutorial]]<nowiki />

@@ Line 1: / Line 1: @@
-[[Category:Tutorials]] [[Category:Basics]]
+[[Category:Tutorials]] [[Category:Basics]]<nowiki />
-[[Category:Tutorials | GPROF Tutorial]]
+[[Category:Tutorials | Gprof Tutorial]]<nowiki />
-{{Hpc_nrw_tutorial_box}}
 Gprof is a free and easy-to-use profiler.
 Profiling applications gives valuable insights into the program structure.