Skip to content
This repository was archived by the owner on Oct 23, 2025. It is now read-only.

Commit fa942f9

Browse files
vmayoraliluetkebsloretz
committed
Address comments about tracing and benchmarking section
Co-authored-by: Ingo Lütkebohle <[email protected]> Co-authored-by: Shane Loretz <[email protected]> Signed-off-by: Víctor Mayoral Vilches <[email protected]>
1 parent 4b98c34 commit fa942f9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

rep-2014.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,11 +96,11 @@ Tracing and benchmarking
9696

9797
Tracing and benchmarking can be defined as follows:
9898

99-
- `tracing`: a technique used to understand what goes on in a running software system.
99+
- `tracing`: logging (partial) execution information while the system is running. `tracing` is used to understand what goes on in a running software system.
100100

101101
- `benchmarking`: a method of comparing the performance of various systems by running a common test.
102102

103-
From these definitions, inherently one can determine that both benchmarking and tracing are connected in the sense that the test/benchmark will use a series of measurements for comparison. These measurements will come from tracing probes. In other words, tracing will collect data that will then be fed into a benchmark program for comparison.
103+
From these definitions, inherently one can determine that both benchmarking and tracing are connected in the sense that the test/benchmark will use a series of measurements for comparison. These measurements will come from tracing probes or other logging mechanisms. In other words, tracing will collect data that will then be fed into a benchmark program for comparison.
104104

105105

106106

0 commit comments

Comments
 (0)