[bootlin/training-materials updates] master: debugging: add more information on tool choice (ee203567)

Clément Léger clement.leger at bootlin.com
Tue Nov 15 18:17:14 CET 2022

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/ee203567e7c68b7cd0caadad2da63769e1dce84c


commit ee203567e7c68b7cd0caadad2da63769e1dce84c
Author: Clément Léger <clement.leger at bootlin.com>
Date:   Tue Nov 15 14:45:10 2022 +0100

    debugging: add more information on tool choice
    Signed-off-by: Clément Léger <clement.leger at bootlin.com>


 .../debugging-system-wide-profiling.tex                           | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex b/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
index dc57fe81..afe9931a 100644
--- a/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
+++ b/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
@@ -1166,9 +1166,15 @@ $ lttng create my-session --set-url=net://remote-system
     \item Before starting to profile or trace, one should know which type of
           tool to use.
+    \item This choice is guided by the level of profiling
+    \item Often start by analyzing/optimizing the application level using
+          application tracing/profiling tools (valgrind, perf, etc).
+    \item Then analyze user space + kernel performances
+    \item Finally, trace or profile the whole system if the performance problems
+          happens only when running under a loaded system.
-      \item For sporadic problems, record traces and analyze them
       \item For "constant" load problems, snapshot tools works fine.
+      \item For sporadic problems, record traces and analyze them.

More information about the training-materials-updates mailing list