From 29dfb151cb8855ce0bf9407fee4f6383ddc6fd2c Mon Sep 17 00:00:00 2001
From: Bartosz Taudul <wolf.pld@gmail.com>
Date: Sun, 5 Apr 2020 16:34:50 +0200
Subject: [PATCH] Add Ryzen execution times example.

---
 manual/images/ryzen.png | Bin 0 -> 921 bytes
 manual/tracy.tex        |  24 ++++++++++++++++++++++++
 2 files changed, 24 insertions(+)
 create mode 100644 manual/images/ryzen.png

diff --git a/manual/images/ryzen.png b/manual/images/ryzen.png
new file mode 100644
index 0000000000000000000000000000000000000000..0c254d59757f60451ee7fa16b3780ba71918a570
GIT binary patch
literal 921
zcmV;K17`e*P)<h;3K|Lk000e1NJLTq00JKX0071T0{{R3NIh^|00009a7bBm001r{
z001r{0eGc9b^rhX2XskIMF->r1r7xq;I|;g0000PbVXQnLvL+uWo~o;Lvm$dbY)~9
zcWHEJAV*0}P*;Ht7XSbN22e~?MF0Q*|NsA`*`M7200RL@L_t(&-tAj4Zre}{eb6a-
zoE#ws=#U#ULxBcp;QSMG?$DtpC^~vb>_2qukgXnqmQxy_LBb(`nUp0v$Z{lEX$(uM
z6-An4NO*ehk)QnhfD^BOS%T$thfS{p4O|1rQvul-JQ+Zq9S9Ac3?OTOjQb^rhY$}S
z&k%$MPX>@jLA*n9q%%yY7a<P4%2>6<ZP>aT>SZYyKw1N_CO~vBb^v)4M7ty>_P|&h
zlC513>5H7$6((MLbDz{7BO8+=(#y0bVAQKp;9F+G9rR@5QK5?=wt67k6**kH^>nls
z>voxV?4Tz#K<@2i+A5RS0Ejnm9@KnvycY}5dX@I|=eI7&p_~-yj2yGBFbSJ&Qi>qj
zoji#fgV4C<%+rRPfZ0}=EPIBNYziVdKkpt(6{%RJt<;mXl0LS=M2nqxzX3TKari_E
zwIldS#YoEUY_d6MLk_Q1SG+AIYU?LT#INvx94eF5hu2>OaVv5x^Kr?NB0Uu42mqpG
z-;+#@m4?!(Ra6pyBkWK48*Su?025&T9suX;wyZyn^i_rFtt>!yVH^hl;u)3Yr%k_s
zW)VP;3J}kQev;*NSn2ilnY5x;HYUgQcP<q;sDat;zZU?3A+i%f`kM+glZqn?*#~H^
ztj93T-VEn0MrY2&vJzyPCby5VsE58-@C-XE_K4<~_(8}O1K9&)4#dl>DISu83*Wwu
zzQV+iy0$ct414MAX&SS4<48D`^j(3S<zvx|oYYXxRS3O8>YLnzkCU(*-B~V<Qd(3h
zhRMo&@98Q5W&mE3Kv`m;8E~3Fp<y|T<#@PK2vz;$<{Hp*066k5cb0!VenYKftlG=f
zX9gHg$j9G(AHg#-2>{%1r6mwq+09*I1U>=OK+~W?2qEOksFF$>a;h3Qr-u8ouu;i+
zyI9nr<e&YYFb9XK0n>o-kJ10#ZiQ%Ec_!fi>+OL+w>zP;BI3mf5Z@x9jZqLjnCzU6
vX0r7I2X^ez^y{bHW|$n+`%~1<Tl3?;7u@7mf2$!500000NkvXXu0mjfU8t8D

literal 0
HcmV?d00001

diff --git a/manual/tracy.tex b/manual/tracy.tex
index 45adf256..f7b49697 100644
--- a/manual/tracy.tex
+++ b/manual/tracy.tex
@@ -520,6 +520,22 @@ Be very careful when using AVX2 or AVX512.
 
 More information can be found at \url{https://travisdowns.github.io/blog/2020/01/17/avxfreq1.html}, \url{https://en.wikichip.org/wiki/intel/frequency_behavior}.
 
+\paragraph{Summing it up}
+\label{ryzen}
+
+Power management schemes employed in various CPUs make it hard to reason about true performance of the code. For example, figure~\ref{ryzenimage} contains a histogram of function execution times (as described in chapter~\ref{findzone}), as measured on an AMD Ryzen CPU. The results ranged from 13.05~\si{\micro\second} to 61.25~\si{\micro\second} (extreme outliers were not included on the graph, limiting the longest displayed time to 36.04~\si{\micro\second}).
+
+\begin{figure}[h]
+\centering
+\includegraphics[width=0.5\textwidth]{images/ryzen.png}
+\caption{Example function execution times on a Ryzen CPU}
+\label{ryzenimage}
+\end{figure}
+
+We can immediately see that there are two distinct peaks, at 13.4~\si{\micro\second} and 15.3~\si{\micro\second}. A reasonable assumption would be that there are two paths in the code, one that can omit some work, and the second one which must do some additional job. But here's a catch -- the measured code is actually branchless and is always executed the same way. The two peaks represent two turbo frequencies between which the CPU was aggressively switching.
+
+We can also see that the graph gradually falls off to the right (representing longer times), with a small bump near the end. This can be attributed to running in power saving mode, with differing reaction times to the required operating frequency boost to full power.
+
 \subsection{Building the server}
 
 The easiest way to get going is to build the data analyzer, available in the \texttt{profiler} directory. With it you can connect to localhost or remote clients and view the collected data right away.
@@ -2371,6 +2387,14 @@ logo=\bclampe
 You may press \keys{\ctrl + F} to open or focus the find zone window and set the keyboard input on the search box.
 \end{bclogo}
 
+\begin{bclogo}[
+noborder=true,
+couleur=black!5,
+logo=\bcattention
+]{Caveats}
+When using the execution times histogram you must be aware about the hardware peculiarities. Read section~\ref{checkenvironmentcpu} for more detail.
+\end{bclogo}
+
 \subsubsection{Timeline interaction}
 
 When the zone statistics are displayed in the find zone menu, matching zones will be highlighted on the timeline display. Highlight colors match the histogram display. Bright blue highlight is used to indicate that a zone is in the optional selection range, while the yellow highlight is used for the rest of zones.