[Chapter7] Added a TODO

chapters/7-Overview-Of-Performance-Analysis-Tools/7-6 Windows ETW.md

@@ -1,3 +1,5 @@
+[TODO]: possible candidate for Appendix
+
 ## Event Tracing for Windows
 
 Microsoft has developed a system-wide tracing facility named Event Tracing for Windows (ETW). It was originally intended for helping device driver developers, but later found its use in analyzing general-purpose applications as well. ETW is available on all supported Windows platforms (x86, x64 and ARM) with the corresponding platform-dependent installation packages. ETW records structured events in user and kernel code with full call stack trace support which allows to observe SW dynamics in a running system and solve many challenging performance issues.

chapters/7-Overview-Of-Performance-Analysis-Tools/7-7 Tracy.md

@@ -1,3 +1,5 @@
+[TODO]: possible candidate for Appendix
+
 ## Specialized and Hybrid profilers {#sec:Tracy}
 
 Most of the tools explored so far fall under the category of sampling profilers. These are great when you want to identify hot-spots in your code, but in some cases they might not provide enough granularity for analysis. Depending on the profiler sampling frequency and the behavior of your program, most functions could be fast enough that they don't show up in a profiler. In some scenarios you might want to manually define which parts of your program need to be measured consistently. Video games, for instance, render frames (the final image shown on screen) on average at 60 frames per second (FPS); some monitors allow up to 144 FPS. At 60 FPS, each frame has as little as 16 milliseconds to complete the work before moving on to the next one. Developers pay particular attention to frames that go above this threshold, as this causes visible stutter in games and can ruin the player experience. This situation is hard to capture with a sampling profiler, as they usually only provide the total time taken for a given function.