Changes in doc/proposals/concurrency/text/results.tex [6090518:5c4f2c2]

File:

• doc/proposals/concurrency/text/results.tex (modified) (3 diffs)

doc/proposals/concurrency/text/results.tex

@@ -40 +40 @@
 All benchmarks are run using the same harness to produce the results, seen as the \code{BENCH()} macro in the following examples. This macro uses the following logic to benchmark the code :
 \begin{pseudo}
-#define BENCH(run, result)
+#define BENCH(run, result) //Param: What to run, variable containing result
         before = gettime();
         run;
@@ -49 +49 @@
 
 \subsection{Context-Switching}
-The first interesting benchmark is to measure how long context-switches take. The simplest approach to do this is to yield on a thread, which executes a 2-step context switch. In order to make the comparison fair, coroutines also execute a 2-step context-switch (\gls{uthread} to \gls{kthread} then \gls{kthread} to \gls{uthread}), which is a resume/suspend cycle instead of a yield. Listing \ref{lst:ctx-switch} shows the code for coroutines and threads with the results in table \ref{tab:ctx-switch}. All omitted tests are functionally identical to one of these tests.
+The first interesting benchmark is to measure how long context-switches take. The simplest approach to do this is to yield on a thread\footnote{Yielding causes the thread to context-switch to the scheduler and back, more precisely: from the \gls{uthread} to the \gls{kthread} then from the \gls{kthread} back to the same \gls{uthread} (or a different one in the general case).}, which executes a 2-step context switch. In order to make the comparison fair, coroutines also execute a 2-step context-switch by resuming another coroutine which does nothing but suspending in a tight loop, which is a resume/suspend cycle instead of a yield. Listing \ref{lst:ctx-switch} shows the code for coroutines and threads with the results in table \ref{tab:ctx-switch}. All omitted tests are functionally identical to one of these tests. The difference between coroutines and threads can be attributed to the cost of scheduling.
 \begin{figure}
 \begin{multicols}{2}
@@ -199 +199 @@
 \multicolumn{1}{c |}{} & \multicolumn{1}{c |}{ Median } &\multicolumn{1}{c |}{ Average } & \multicolumn{1}{c |}{ Standard Deviation} \\
 \hline
+Pthreads Condition Variable                     & 5902.5        & 6093.29       & 714.78 \\
 \uC \code{signal}                                       & 322           & 323   & 3.36   \\
 \CFA \code{signal}, 1 \code{monitor}    & 352.5 & 353.11        & 3.66   \\