[bootlin/training-materials updates] master: debugging course: "performances" -> "performance" (c2936ad9)

[Michael Opdenacker]

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

>---------------------------------------------------------------

commit c2936ad9be90d718c8c4500b109350e18f6aaa64
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Nov 28 12:05:05 2022 +0100

    debugging course: "performances" -> "performance"
    
    "Performance" is uncountable in English, at least
    for the meaning used in this context.
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

c2936ad9be90d718c8c4500b109350e18f6aaa64
 agenda/debugging-agenda.tex                                       | 2 +-
 agenda/debugging-online-agenda.tex                                | 2 +-
 .../debugging-application-profiling.tex                           | 4 ++--
 .../debugging-system-wide-profiling.tex                           | 2 +-
 .../debugging-application-profiling.tex                           | 8 ++++----
 slides/debugging-principles/debugging-principles.tex              | 2 +-
 .../debugging-system-wide-profiling.tex                           | 2 +-
 7 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/agenda/debugging-agenda.tex b/agenda/debugging-agenda.tex
index 55804838..ee8f8794 100644
--- a/agenda/debugging-agenda.tex
+++ b/agenda/debugging-agenda.tex
@@ -225,7 +225,7 @@
   \begin{itemize}
   \item Profiling an application with {\em Callgrind}/{\em
       KCachegrind}.
-  \item Analyzing application performances with {\em perf}.
+  \item Analyzing application performance with {\em perf}.
   \item Generating a flamegraph using {\em FlameGraph}.
   \end{itemize}
 }
diff --git a/agenda/debugging-online-agenda.tex b/agenda/debugging-online-agenda.tex
index 9e307c6c..a90708fc 100644
--- a/agenda/debugging-online-agenda.tex
+++ b/agenda/debugging-online-agenda.tex
@@ -232,7 +232,7 @@
   \begin{itemize}
   \item Profiling an application with {\em Callgrind}/{\em
       KCachegrind}.
-  \item Analyzing application performances with {\em perf}.
+  \item Analyzing application performance with {\em perf}.
   \item Generating a flamegraph using {\em FlameGraph}.
   \end{itemize}
 }
diff --git a/labs/debugging-application-profiling/debugging-application-profiling.tex b/labs/debugging-application-profiling/debugging-application-profiling.tex
index e0ed516f..9667591c 100644
--- a/labs/debugging-application-profiling/debugging-application-profiling.tex
+++ b/labs/debugging-application-profiling/debugging-application-profiling.tex
@@ -5,7 +5,7 @@
     \item Visualizing application heap using {\em Massif}.
     \item Profiling an application with {\em Cachegrind}, {\em Callgrind} and
           {\em KCachegrind}.
-    \item Analyzing application performances with {\em perf}.
+    \item Analyzing application performance with {\em perf}.
   \end{itemize}
 }
 
@@ -91,7 +91,7 @@ CPU time
 
 \section{Perf}
 
-In order to have a better view of the performances of our program in a real
+In order to have a better view of the performance of our program in a real
 system, we will use \code{perf}. First of all, we will record our program
 execution using the \code{perf record} command.
 
diff --git a/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex b/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
index b5c88c84..195d5963 100644
--- a/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
+++ b/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
@@ -93,7 +93,7 @@ Reanalyze the traces with kernel shark and try to understand what is going on.
 
 \section{LTTng}
 
-In order to observe our program performances, we want to instrument it with
+In order to observe our program performance, we want to instrument it with
 tracepoints. We would like to know how much times it takes to compute the
 crc32 of a specific buffer.
 
diff --git a/slides/debugging-application-profiling/debugging-application-profiling.tex b/slides/debugging-application-profiling/debugging-application-profiling.tex
index d01d6f30..823770ca 100644
--- a/slides/debugging-application-profiling/debugging-application-profiling.tex
+++ b/slides/debugging-application-profiling/debugging-application-profiling.tex
@@ -9,8 +9,8 @@
           in the code or leverage kernel/userspace mechanisms.
     \begin{itemize}
       \item Profiling function calls and count of calls allow to optimize
-            performances.
-      \item Profiling processor usage allows to optimize performances and
+            performance.
+      \item Profiling processor usage allows to optimize performance and
             reduce power usage.
       \item Profiling memory usage allows to optimize memory consumption.
     \end{itemize}
@@ -260,7 +260,7 @@ Histogram for block sizes:
           hardware resources are used.
     \item Many hardware elements can have an impact on the program execution:
     \begin{itemize}
-      \item Cache performances can be degraded by an application without memory
+      \item Cache performance can be degraded by an application without memory
             spatial locality.
       \item Page miss due to using too much memory without spatial locality.
       \item Alignment faults when doing misaligned accesses.
@@ -425,6 +425,6 @@ $ valgrind --tool=callgrind ./my_program
     \item Profiling application heap using {\em Massif}.
     \item Profiling an application with {\em Cachegrind}, {\em Callgrind} and
           {\em KCachegrind}.
-    \item Analyzing application performances with {\em perf}.
+    \item Analyzing application performance with {\em perf}.
   \end{itemize}
 }
diff --git a/slides/debugging-principles/debugging-principles.tex b/slides/debugging-principles/debugging-principles.tex
index 549ede04..3a7a2f32 100644
--- a/slides/debugging-principles/debugging-principles.tex
+++ b/slides/debugging-principles/debugging-principles.tex
@@ -46,7 +46,7 @@
     \item Analysis at program runtime to assist performance optimizations
     \item Often achieved by sampling counters during execution
     \item Uses specific tools, libraries and operating system features to
-          measure performances.
+          measure performance.
     \begin{itemize}
       \item Using {\em perf}, {\em OProfile} for instance.
     \end{itemize}
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 8ad2c1ac..141345f8 100644
--- a/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
+++ b/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
@@ -1193,7 +1193,7 @@ $ lttng create my-session --set-url=net://remote-system
     \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 Then analyze user space + kernel performance
     \item Finally, trace or profile the whole system if the performance problems
           happens only when running under a loaded system.
     \begin{itemize}