Ignore:
Timestamp:
Aug 16, 2022, 2:52:24 PM (4 years ago)
Author:
Thierry Delisle <tdelisle@…>
Branches:
ADT, ast-experimental, master, pthread-emulation, stuck-waitfor-destruct
Children:
71cf630
Parents:
32d1383 (diff), e116db3 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Merge branch 'master' of plg.uwaterloo.ca:software/cfa/cfa-cc

File:
1 edited

Legend:

Unmodified
Added
Removed

  • doc/theses/thierry_delisle_PhD/thesis/text/eval_micro.tex

    r32d1383 r17c6edeb  
    44This chapter presents five different experimental setup, evaluating some of the basic features of \CFA's scheduler.
    55
    6 \section{Benchmark Environment}
     6\section{Benchmark Environment}\label{microenv}
    77All benchmarks are run on two distinct hardware platforms.
    88\begin{description}
    … …  
    3232        \centering
    3333        \input{cycle.pstex_t}
    34         \caption[Cycle benchmark]{Cycle benchmark\smallskip\newline Each \gls{at} unparks the next \gls{at} in the cycle before parking itself.}
     34        \caption[Cycle benchmark]{Cycle benchmark\smallskip\newline Each \at unparks the next \at in the cycle before parking itself.}
    3535        \label{fig:cycle}
    3636\end{figure}
    3737The most basic evaluation of any ready queue is to evaluate the latency needed to push and pop one element from the ready queue.
    3838Since these two operation also describe a @yield@ operation, many systems use this operation as the most basic benchmark.
    39 However, yielding can be treated as a special case by optimizing it away (dead code) since the number of ready \glspl{at} does not change.
    40 Not all systems perform this optimization, but those that do have an artificial performance benefit because the yield becomes a \emph{nop}.
     39However, yielding can be treated as a special case and some aspects of the scheduler can be optimized away since the number of ready \ats does not change.
     40Not all systems perform this type of optimization, but those that do have an artificial performance benefit because the yield becomes a \emph{nop}.
    4141For this reason, I chose a different first benchmark, called \newterm{Cycle Benchmark}.
    42 This benchmark arranges a number of \glspl{at} into a ring, as seen in Figure~\ref{fig:cycle}, where the ring is a circular singly-linked list.
    43 At runtime, each \gls{at} unparks the next \gls{at} before parking itself.
    44 Unparking the next \gls{at} pushes that \gls{at} onto the ready queue as does the ensuing park.
    45 
    46 Hence, the underlying runtime cannot rely on the number of ready \glspl{at} staying constant over the duration of the experiment.
    47 In fact, the total number of \glspl{at} waiting on the ready queue is expected to vary because of the race between the next \gls{at} unparking and the current \gls{at} parking.
     42This benchmark arranges a number of \ats into a ring, as seen in Figure~\ref{fig:cycle}, where the ring is a circular singly-linked list.
     43At runtime, each \at unparks the next \at before parking itself.
     44Unparking the next \at pushes that \at onto the ready queue while the ensuing park leads to a \at being popped from the ready queue.
     45
     46Hence, the underlying runtime cannot rely on the number of ready \ats staying constant over the duration of the experiment.
     47In fact, the total number of \ats waiting on the ready queue is expected to vary because of the delay between the next \at unparking and the current \at parking.
    4848That is, the runtime cannot anticipate that the current task will immediately park.
    49 As well, the size of the cycle is also decided based on this race, \eg a small cycle may see the chain of unparks go full circle before the first \gls{at} parks because of time-slicing or multiple \procs.
    50 Every runtime system must handle this race and cannot optimized away the ready-queue pushes and pops.
    51 To prevent any attempt of silently omitting ready-queue operations, the ring of \glspl{at} is made big enough so the \glspl{at} have time to fully park before being unparked again.
    52 (Note, an unpark is like a V on a semaphore, so the subsequent park (P) may not block.)
     49As well, the size of the cycle is also decided based on this delay.
     50Note that, an unpark is like a V on a semaphore, so the subsequent park (P) may not block.
     51If this happens, the scheduler push and pop are avoided and the results of the experiment would be skewed.
     52Because of time-slicing or because cycles can be spread over multiple \procs, a small cycle may see the chain of unparks go full circle before the first \at parks.
     53Every runtime system must handle this race and but cannot optimized away the ready-queue pushes and pops if the cycle is long enough.
     54To prevent any attempt of silently omitting ready-queue operations, the ring of \ats is made big enough so the \ats have time to fully park before being unparked again.
    5355Finally, to further mitigate any underlying push/pop optimizations, especially on SMP machines, multiple rings are created in the experiment.
    54 
    55 To avoid this benchmark being affected by idle-sleep handling, the number of rings is multiple times greater than the number of \glspl{proc}.
    56 This design avoids the case where one of the \glspl{proc} runs out of work because of the variation on the number of ready \glspl{at} mentioned above.
    5756
    5857Figure~\ref{fig:cycle:code} shows the pseudo code for this benchmark.
    … …  
    6463        count := 0
    6564        for {
     65                @this.next.wake()@
    6666                @wait()@
    67                 @this.next.wake()@
    6867                count ++
    6968                if must_stop() { break }
    … …  
    7776
    7877\subsection{Results}
    79 Figure~\ref{fig:cycle:jax} shows the throughput as a function of \proc count, where each run uses 100 cycles per \proc and 5 \ats per cycle.
    80 
    81 \begin{figure}
    82         \subfloat[][Throughput, 100 \ats per \proc]{
     78\begin{figure}
     79        \subfloat[][Throughput, 100 cycles per \proc]{
    8380                \resizebox{0.5\linewidth}{!}{
    8481                        \input{result.cycle.jax.ops.pstex_t}
    … …  
    8683                \label{fig:cycle:jax:ops}
    8784        }
    88         \subfloat[][Throughput, 1 \ats per \proc]{
     85        \subfloat[][Throughput, 1 cycle per \proc]{
    8986                \resizebox{0.5\linewidth}{!}{
    9087                        \input{result.cycle.low.jax.ops.pstex_t}
    … …  
    9390        }
    9491
    95         \subfloat[][Latency, 100 \ats per \proc]{
     92        \subfloat[][Scalability, 100 cycles per \proc]{
    9693                \resizebox{0.5\linewidth}{!}{
    9794                        \input{result.cycle.jax.ns.pstex_t}
    9895                }
    99 
    100         }
    101         \subfloat[][Latency, 1 \ats per \proc]{
     96                \label{fig:cycle:jax:ns}
     97        }
     98        \subfloat[][Scalability, 1 cycle per \proc]{
    10299                \resizebox{0.5\linewidth}{!}{
    103100                        \input{result.cycle.low.jax.ns.pstex_t}
    … …  
    105102                \label{fig:cycle:jax:low:ns}
    106103        }
    107         \caption[Cycle Benchmark on Intel]{Cycle Benchmark on Intel\smallskip\newline Throughput as a function of \proc count with 100 cycles per \proc and 5 \ats per cycle.}
     104        \caption[Cycle Benchmark on Intel]{Cycle Benchmark on Intel\smallskip\newline Throughput and Scalability as a function of \proc count 5 \ats per cycle and different cycle count. For Throughput higher is better, for Scalability lower is better. Each series represent 15 independent runs, the dotted lines are extremums while the solid line is the medium.}
    108105        \label{fig:cycle:jax}
    109106\end{figure}
    110107
    111 \todo{results discussion}
     108\begin{figure}
     109        \subfloat[][Throughput, 100 cycles per \proc]{
     110                \resizebox{0.5\linewidth}{!}{
     111                        \input{result.cycle.nasus.ops.pstex_t}
     112                }
     113                \label{fig:cycle:nasus:ops}
     114        }
     115        \subfloat[][Throughput, 1 cycle per \proc]{
     116                \resizebox{0.5\linewidth}{!}{
     117                        \input{result.cycle.low.nasus.ops.pstex_t}
     118                }
     119                \label{fig:cycle:nasus:low:ops}
     120        }
     121
     122        \subfloat[][Scalability, 100 cycles per \proc]{
     123                \resizebox{0.5\linewidth}{!}{
     124                        \input{result.cycle.nasus.ns.pstex_t}
     125                }
     126                \label{fig:cycle:nasus:ns}
     127        }
     128        \subfloat[][Scalability, 1 cycle per \proc]{
     129                \resizebox{0.5\linewidth}{!}{
     130                        \input{result.cycle.low.nasus.ns.pstex_t}
     131                }
     132                \label{fig:cycle:nasus:low:ns}
     133        }
     134        \caption[Cycle Benchmark on AMD]{Cycle Benchmark on AMD\smallskip\newline Throughput and Scalability as a function of \proc count 5 \ats per cycle and different cycle count. For Throughput higher is better, for Scalability lower is better. Each series represent 15 independent runs, the dotted lines are extremums while the solid line is the medium.}
     135        \label{fig:cycle:nasus}
     136\end{figure}
     137Figure~\ref{fig:cycle:jax} and Figure~\ref{fig:cycle:nasus} shows the throughput as a function of \proc count on Intel and AMD respectively, where each cycle has 5 \ats.
     138The graphs show traditional throughput on the top row and \newterm{scalability} on the bottom row.
     139Where scalability uses the same data but the Y axis is calculated as the number of \procs over the throughput.
     140In this representation, perfect scalability should appear as a horizontal line, \eg, if doubling the number of \procs doubles the throughput, then the relation stays the same.
     141The left column shows results for 100 cycles per \proc, enough cycles to always keep every \proc busy.
     142The right column shows results for only 1 cycle per \proc, where the ready queues are expected to be near empty at all times.
     143The distinction is meaningful because the idle sleep subsystem is expected to matter only in the right column, where spurious effects can cause a \proc to run out of work temporarily.
     144
     145The experiment was run 15 times for each series and processor count and the \emph{$\times$}s on the graph show all of the results obtained.
     146Each series also has a solid and two dashed lines highlighting the median, maximum and minimum result respectively.
     147This presentation offers an overview of the distribution of the results for each series.
     148
     149The experimental setup uses taskset to limit the placement of \glspl{kthrd} by the operating system.
     150As mentioned in Section~\ref{microenv}, the experiement is setup to prioritize running on 2 \glspl{hthrd} per core before running on multiple sockets.
     151For the Intel machine, this means that from 1 to 24 \procs, one socket and \emph{no} hyperthreading is used and from 25 to 48 \procs, still only one socket but \emph{with} hyperthreading.
     152This pattern is repeated between 49 and 96, between 97 and 144, and between 145 and 192.
     153On AMD, the same algorithm is used, but the machine only has 2 sockets.
     154So hyperthreading\footnote{Hyperthreading normally refers specifically to the technique used by Intel, however here it is loosely used to refer to AMD's equivalent feature.} is used when the \proc count reach 65 and 193.
     155
     156Figure~\ref{fig:cycle:jax:ops} and Figure~\ref{fig:cycle:jax:ns} show that for 100 cycles per \proc, \CFA, Go and Tokio all obtain effectively the same performance.
     157Libfibre is slightly behind in this case but still scales decently.
     158As a result of the \gls{kthrd} placement, we can see that additional \procs from 25 to 48 offer less performance improvements for all runtimes.
     159As expected, this pattern repeats between \proc count 72 and 96.
     160The performance goal of \CFA is to obtain equivalent performance to other, less fair schedulers and that is what results show.
     161Figure~\ref{fig:cycle:jax:ops} and \ref{fig:cycle:jax:ns} show very good throughput and scalability for all runtimes.
     162
     163When running only a single cycle, the story is slightly different.
     164\CFA and tokio obtain very smiliar results overall, but tokio shows notably more variations in the results.
     165While \CFA, Go and tokio achive equivalent performance with 100 cycles per \proc, with only 1 cycle per \proc Go achieves slightly better performance.
     166This difference in throughput and scalability is due to the idle-sleep mechanism.
     167With very few cycles, stealing or helping can cause a cascade of tasks migration and trick \proc into very short idle sleeps.
     168Both effect will negatively affect performance.
     169
     170An interesting and unusual result is that libfibre achieves better performance with fewer cycle.
     171This suggest that the cascade effect is never present in libfibre and that some bottleneck disappears in this context.
     172However, I did not investigate this result any deeper.
     173
     174Figure~\ref{fig:cycle:nasus} show a similar story happening on AMD as it does on Intel.
     175The different performance improvements and plateaus due to cache topology appear at the expected \proc counts of 64, 128 and 192, for the same reasons as on Intel.
     176Unlike Intel, on AMD all 4 runtimes achieve very similar throughput and scalability for 100 cycles per \proc.
     177
     178In the 1 cycle per \proc experiment, the same performance increase for libfibre is visible.
     179However, unlike on Intel, tokio achieves the same performance as Go rather than \CFA.
     180This leaves \CFA trailing behind in this particular case, but only at hight core counts.
     181Presumably this is because in this case, \emph{any} helping is likely to cause a cascade of \procs running out of work and attempting to steal.
     182Since this effect is only problematic in cases with 1 \at per \proc it is not very meaningful for the general performance.
     183
     184The conclusion from both architectures is that all of the compared runtime have fairly equivalent performance in this scenario.
     185Which demonstrate that in this case \CFA achieves equivalent performance.
    112186
    113187\section{Yield}
    114188For completion, the classic yield benchmark is included.
    115 This benchmark is simpler than the cycle test: it creates many \glspl{at} that call @yield@.
     189This benchmark is simpler than the cycle test: it creates many \ats that call @yield@.
    116190As mentioned, this benchmark may not be representative because of optimization shortcuts in @yield@.
    117 The only interesting variable in this benchmark is the number of \glspl{at} per \glspl{proc}, where ratios close to 1 means the ready queue(s) can be empty.
     191The only interesting variable in this benchmark is the number of \ats per \procs, where ratios close to 1 means the ready queue(s) can be empty.
    118192This scenario can put a strain on the idle-sleep handling compared to scenarios where there is plenty of work.
    119193Figure~\ref{fig:yield:code} shows pseudo code for this benchmark, where the @wait/next.wake@ is replaced by @yield@.
    … …  
    136210
    137211\subsection{Results}
    138 
    139 Figure~\ref{fig:yield:jax} shows the throughput as a function of \proc count, where each run uses 100 \ats per \proc.
    140 
    141212\begin{figure}
    142213        \subfloat[][Throughput, 100 \ats per \proc]{
    … …  
    153224        }
    154225
    155         \subfloat[][Latency, 100 \ats per \proc]{
     226        \subfloat[][Scalability, 100 \ats per \proc]{
    156227                \resizebox{0.5\linewidth}{!}{
    157228                \input{result.yield.jax.ns.pstex_t}
    … …  
    159230                \label{fig:yield:jax:ns}
    160231        }
    161         \subfloat[][Latency, 1 \ats per \proc]{
     232        \subfloat[][Scalability, 1 \ats per \proc]{
    162233                \resizebox{0.5\linewidth}{!}{
    163234                \input{result.yield.low.jax.ns.pstex_t}
    … …  
    165236                \label{fig:yield:jax:low:ns}
    166237        }
    167         \caption[Yield Benchmark on Intel]{Yield Benchmark on Intel\smallskip\newline Throughput as a function of \proc count, using 1 \ats per \proc.}
     238        \caption[Yield Benchmark on Intel]{Yield Benchmark on Intel\smallskip\newline Throughput and Scalability as a function of \proc count, using 1 \ats per \proc. For Throughput higher is better, for Scalability lower is better. Each series represent 15 independent runs, the dotted lines are extremums while the solid line is the medium.}
    168239        \label{fig:yield:jax}
    169240\end{figure}
    170241
    171 \todo{results discussion}
     242\begin{figure}
     243        \subfloat[][Throughput, 100 \ats per \proc]{
     244                \resizebox{0.5\linewidth}{!}{
     245                        \input{result.yield.nasus.ops.pstex_t}
     246                }
     247                \label{fig:yield:nasus:ops}
     248        }
     249        \subfloat[][Throughput, 1 \at per \proc]{
     250                \resizebox{0.5\linewidth}{!}{
     251                        \input{result.yield.low.nasus.ops.pstex_t}
     252                }
     253                \label{fig:yield:nasus:low:ops}
     254        }
     255
     256        \subfloat[][Scalability, 100 \ats per \proc]{
     257                \resizebox{0.5\linewidth}{!}{
     258                        \input{result.yield.nasus.ns.pstex_t}
     259                }
     260                \label{fig:yield:nasus:ns}
     261        }
     262        \subfloat[][Scalability, 1 \at per \proc]{
     263                \resizebox{0.5\linewidth}{!}{
     264                        \input{result.yield.low.nasus.ns.pstex_t}
     265                }
     266                \label{fig:yield:nasus:low:ns}
     267        }
     268        \caption[Yield Benchmark on AMD]{Yield Benchmark on AMD\smallskip\newline Throughput and Scalability as a function of \proc count, using 1 \ats per \proc. For Throughput higher is better, for Scalability lower is better. Each series represent 15 independent runs, the dotted lines are extremums while the solid line is the medium.}
     269        \label{fig:yield:nasus}
     270\end{figure}
     271Figure~\ref{fig:yield:jax} shows the throughput as a function of \proc count on Intel.
     272It is fairly obvious why I claim this benchmark is more artificial.
     273The throughput is dominated by the mechanism used to handle the @yield@.
     274\CFA does not have special handling for @yield@ but the experiment requires less synchronization.
     275As a result achieves better performance than the cycle benchmark, but still comparable.
     276
     277When the number of \ats is reduce to 1 per \proc, the cost of idle sleep also comes into play in a very significant way.
     278If anything causes a \at migration, where two \ats end-up on the same ready-queue, work-stealing will start occuring and could cause several \ats to shuffle around.
     279In the process, several \procs can go to sleep transiently if they fail to find where the \ats were shuffled to.
     280In \CFA, spurious bursts of latency can trick a \proc into helping, triggering this effect.
     281However, since user-level threading with equal number of \ats and \procs is a somewhat degenerate case, especially when context-switching very often, this result is not particularly meaningful and is only included for completness.
     282
     283Libfibre uses the fact that @yield@ doesn't change the number of ready fibres and by-passes the idle-sleep mechanism entirely, producing significantly better throughput.
     284Additionally, when only running 1 \at per \proc, libfibre optimizes further and forgoes the context-switch entirely.
     285This results in incredible performance results comparing to the other runtimes.
     286
     287In stark contrast with libfibre, Go puts yielding goroutines on a secondary global ready-queue, giving them lower priority.
     288The result is that multiple \glspl{hthrd} contend for the global queue and performance suffers drastically.
     289Based on the scalability, Tokio obtains the similarly poor performance and therefore it is likely it handles @yield@ in a similar fashion.
     290However, it must be doing something different since it does scale at low \proc count.
     291
     292Again, Figure~\ref{fig:yield:nasus} show effectively the same story happening on AMD as it does on Intel.
     293\CFA fairs slightly better with many \ats per \proc, but the performance is satisfactory on both architectures.
     294
     295Since \CFA obtains the same satisfactory performance as the previous benchmark this is still a success, albeit a less meaningful one.
     296
    172297
    173298\section{Churn}
    174299The Cycle and Yield benchmark represent an \emph{easy} scenario for a scheduler, \eg an embarrassingly parallel application.
    175 In these benchmarks, \glspl{at} can be easily partitioned over the different \glspl{proc} upfront and none of the \glspl{at} communicate with each other.
    176 
    177 The Churn benchmark represents more chaotic execution, where there is no relation between the last \gls{proc} on which a \gls{at} ran and blocked and the \gls{proc} that subsequently unblocks it.
    178 With processor-specific ready-queues, when a \gls{at} is unblocked by a different \gls{proc} that means the unblocking \gls{proc} must either ``steal'' the \gls{at} from another processor or find it on a global queue.
    179 This dequeuing results in either contention on the remote queue and/or \glspl{rmr} on \gls{at} data structure.
    180 In either case, this benchmark aims to highlight how each scheduler handles these cases, since both cases can lead to performance degradation if not handled correctly.
     300In these benchmarks, \ats can be easily partitioned over the different \procs upfront and none of the \ats communicate with each other.
     301
     302The Churn benchmark represents more chaotic executions, where there is more communication among \ats but no apparent relation between the last \proc on which a \at ran and blocked, and the \proc that subsequently unblocks it.
     303With processor-specific ready-queues, when a \at is unblocked by a different \proc that means the unblocking \proc must either ``steal'' the \at from another processor or place it on a remote queue.
     304This enqueuing results in either contention on the remote queue and/or \glspl{rmr} on the \at data structure.
     305In either case, this benchmark aims to measure how well each scheduler handles these cases, since both cases can lead to performance degradation if not handled correctly.
    181306
    182307This benchmark uses a fixed-size array of counting semaphores.
    183 Each \gls{at} picks a random semaphore, @V@s it to unblock any \at waiting, and then @P@s on the semaphore.
    184 This creates a flow where \glspl{at} push each other out of the semaphores before being pushed out themselves.
    185 For this benchmark to work, the number of \glspl{at} must be equal or greater than the number of semaphores plus the number of \glspl{proc}.
     308Each \at picks a random semaphore, @V@s it to unblock any \at waiting, and then @P@s on the semaphore.
     309This creates a flow where \ats push each other out of the semaphores before being pushed out themselves.
     310For this benchmark to work, the number of \ats must be equal or greater than the number of semaphores plus the number of \procs.
    186311Note, the nature of these semaphores mean the counter can go beyond 1, which can lead to nonblocking calls to @P@.
    187312Figure~\ref{fig:churn:code} shows pseudo code for this benchmark, where the @yield@ is replaced by @V@ and @P@.
    … …  
    206331
    207332\subsection{Results}
    208 Figure~\ref{fig:churn:jax} shows the throughput as a function of \proc count, where each run uses 100 cycles per \proc and 5 \ats per cycle.
    209 
    210333\begin{figure}
    211334        \subfloat[][Throughput, 100 \ats per \proc]{
    … …  
    215338                \label{fig:churn:jax:ops}
    216339        }
    217         \subfloat[][Throughput, 1 \ats per \proc]{
     340        \subfloat[][Throughput, 2 \ats per \proc]{
    218341                \resizebox{0.5\linewidth}{!}{
    219342                        \input{result.churn.low.jax.ops.pstex_t}
    … …  
    226349                        \input{result.churn.jax.ns.pstex_t}
    227350                }
    228 
    229         }
    230         \subfloat[][Latency, 1 \ats per \proc]{
     351                \label{fig:churn:jax:ns}
     352        }
     353        \subfloat[][Latency, 2 \ats per \proc]{
    231354                \resizebox{0.5\linewidth}{!}{
    232355                        \input{result.churn.low.jax.ns.pstex_t}
    … …  
    234357                \label{fig:churn:jax:low:ns}
    235358        }
    236         \caption[Churn Benchmark on Intel]{\centering Churn Benchmark on Intel\smallskip\newline Throughput and latency of the Churn on the benchmark on the Intel machine.
    237         Throughput is the total operation per second across all cores. Latency is the duration of each operation.}
     359        \caption[Churn Benchmark on Intel]{\centering Churn Benchmark on Intel\smallskip\newline Throughput and latency of the Churn on the benchmark on the Intel machine. For Throughput higher is better, for Scalability lower is better. Each series represent 15 independent runs, the dotted lines are extremums while the solid line is the medium.}
    238360        \label{fig:churn:jax}
    239361\end{figure}
    240362
    241 \todo{results discussion}
     363\begin{figure}
     364        \subfloat[][Throughput, 100 \ats per \proc]{
     365                \resizebox{0.5\linewidth}{!}{
     366                        \input{result.churn.nasus.ops.pstex_t}
     367                }
     368                \label{fig:churn:nasus:ops}
     369        }
     370        \subfloat[][Throughput, 2 \ats per \proc]{
     371                \resizebox{0.5\linewidth}{!}{
     372                        \input{result.churn.low.nasus.ops.pstex_t}
     373                }
     374                \label{fig:churn:nasus:low:ops}
     375        }
     376
     377        \subfloat[][Latency, 100 \ats per \proc]{
     378                \resizebox{0.5\linewidth}{!}{
     379                        \input{result.churn.nasus.ns.pstex_t}
     380                }
     381                \label{fig:churn:nasus:ns}
     382        }
     383        \subfloat[][Latency, 2 \ats per \proc]{
     384                \resizebox{0.5\linewidth}{!}{
     385                        \input{result.churn.low.nasus.ns.pstex_t}
     386                }
     387                \label{fig:churn:nasus:low:ns}
     388        }
     389        \caption[Churn Benchmark on AMD]{\centering Churn Benchmark on AMD\smallskip\newline Throughput and latency of the Churn on the benchmark on the AMD machine.
     390        For Throughput higher is better, for Scalability lower is better. Each series represent 15 independent runs, the dotted lines are extremums while the solid line is the medium.}
     391        \label{fig:churn:nasus}
     392\end{figure}
     393Figure~\ref{fig:churn:jax} and Figure~\ref{fig:churn:nasus} show the throughput as a function of \proc count on Intel and AMD respectively.
     394It uses the same representation as the previous benchmark : 15 runs where the dashed line show the extremums and the solid line the median.
     395The performance cost of crossing the cache boundaries is still visible at the same \proc count.
     396However, this benchmark has performance dominated by the cache traffic as \proc are constantly accessing the eachother's data.
     397Scalability is notably worst than the previous benchmarks since there is inherently more communication between processors.
     398Indeed, once the number of \glspl{hthrd} goes beyond a single socket, performance ceases to improve.
     399An interesting aspect to note here is that the runtimes differ in how they handle this situation.
     400Indeed, when a \proc unparks a \at that was last run on a different \proc, the \at could be appended to the ready-queue local \proc or to the ready-queue of the remote \proc, which previously ran the \at.
     401\CFA, tokio and Go all use the approach of unparking to the local \proc while Libfibre unparks to the remote \proc.
     402In this particular benchmark, the inherent chaos of the benchmark in addition to small memory footprint means neither approach wins over the other.
     403
     404Like for the cycle benchmark, here all runtimes achieve fairly similar performance.
     405Performance improves as long as all \procs fit on a single socket.
     406Beyond that performance starts to suffer from increased caching costs.
     407
     408Indeed on Figures~\ref{fig:churn:jax:ops} and \ref{fig:churn:jax:ns} show that with 1 and 100 \ats per \proc, \CFA, libfibre, Go and tokio achieve effectively equivalent performance for most \proc count.
     409
     410However, Figure~\ref{fig:churn:nasus} again shows a somewhat different story on AMD.
     411While \CFA, libfibre, and tokio achieve effectively equivalent performance for most \proc count, Go starts with better scaling at very low \proc counts but then performance quickly plateaus, resulting in worse performance at higher \proc counts.
     412This performance difference is visible at both high and low \at counts.
     413
     414One possible explanation for this difference is that since Go has very few available concurrent primitives, a channel was used instead of a semaphore.
     415On paper a semaphore can be replaced by a channel and with zero-sized objects passed along equivalent performance could be expected.
     416However, in practice there can be implementation difference between the two.
     417This is especially true if the semaphore count can get somewhat high.
     418Note that this replacement is also made in the cycle benchmark, however in that context it did not seem to have a notable impact.
     419
     420As second possible explanation is that Go may sometimes use the heap when allocating variables based on the result of escape analysis of the code.
     421It is possible that variables that should be placed on the stack are placed on the heap.
     422This could cause extra pointer chasing in the benchmark, heightning locality effects.
     423Depending on how the heap is structure, this could also lead to false sharing.
     424
     425The objective of this benchmark is to demonstrate that unparking \ats from remote \procs do not cause too much contention on the local queues.
     426Indeed, the fact all runtimes achieve some scaling at lower \proc count demontrate that migrations do not need to be serialized.
     427Again these result demonstrate \CFA achieves satisfactory performance.
    242428
    243429\section{Locality}
    244 
    245 \todo{code, setup, results}
     430\begin{figure}
     431\begin{cfa}
     432Thread.main() {
     433        count := 0
     434        for {
     435                r := random() % len(spots)
     436                // go through the array
     437                @work( a )@
     438                spots[r].V()
     439                spots[r].P()
     440                count ++
     441                if must_stop() { break }
     442        }
     443        global.count += count
     444}
     445\end{cfa}
     446\begin{cfa}
     447Thread.main() {
     448        count := 0
     449        for {
     450                r := random() % len(spots)
     451                // go through the array
     452                @work( a )@
     453                // pass array to next thread
     454                spots[r].V( @a@ )
     455                @a = @spots[r].P()
     456                count ++
     457                if must_stop() { break }
     458        }
     459        global.count += count
     460}
     461\end{cfa}
     462\caption[Locality Benchmark : Pseudo Code]{Locality Benchmark : Pseudo Code}
     463\label{fig:locality:code}
     464\end{figure}
     465As mentionned in the churn benchmark, when unparking a \at, it is possible to either unpark to the local or remote ready-queue.
     466\footnote{It is also possible to unpark to a third unrelated ready-queue, but without additional knowledge about the situation, there is little to suggest this would not degrade performance.}
     467The locality experiment includes two variations of the churn benchmark, where an array of data is added.
     468In both variations, before @V@ing the semaphore, each \at increment random cells inside the array.
     469The @share@ variation then passes the array to the shadow-queue of the semaphore, transferring ownership of the array to the woken thread.
     470In the @noshare@ variation the array is not passed on and each thread continously accesses its private array.
     471
     472The objective here is to highlight the different decision made by the runtime when unparking.
     473Since each thread unparks a random semaphore, it means that it is unlikely that a \at will be unparked from the last \proc it ran on.
     474In the @share@ version, this means that unparking the \at on the local \proc is appropriate since the data was last modified on that \proc.
     475In the @noshare@ version, the unparking the \at on the remote \proc is the appropriate approach.
     476
     477The expectation for this benchmark is to see a performance inversion, where runtimes will fare notably better in the variation which matches their unparking policy.
     478This should lead to \CFA, Go and Tokio achieving better performance in @share@ while libfibre achieves better performance in @noshare@.
     479Indeed, \CFA, Go and Tokio have the default policy of unpark \ats on the local \proc, where as libfibre has the default policy of unparks \ats wherever they last ran.
     480
     481\subsection{Results}
     482\begin{figure}
     483        \subfloat[][Throughput share]{
     484                \resizebox{0.5\linewidth}{!}{
     485                        \input{result.locality.share.jax.ops.pstex_t}
     486                }
     487                \label{fig:locality:jax:share:ops}
     488        }
     489        \subfloat[][Throughput noshare]{
     490                \resizebox{0.5\linewidth}{!}{
     491                        \input{result.locality.noshare.jax.ops.pstex_t}
     492                }
     493                \label{fig:locality:jax:noshare:ops}
     494        }
     495
     496        \subfloat[][Scalability share]{
     497                \resizebox{0.5\linewidth}{!}{
     498                        \input{result.locality.share.jax.ns.pstex_t}
     499                }
     500                \label{fig:locality:jax:share:ns}
     501        }
     502        \subfloat[][Scalability noshare]{
     503                \resizebox{0.5\linewidth}{!}{
     504                        \input{result.locality.noshare.jax.ns.pstex_t}
     505                }
     506                \label{fig:locality:jax:noshare:ns}
     507        }
     508        \caption[Locality Benchmark on Intel]{Locality Benchmark on Intel\smallskip\newline Throughput and Scalability as a function of \proc count. For Throughput higher is better, for Scalability lower is better. Each series represent 15 independent runs, the dotted lines are extremums while the solid line is the medium.}
     509        \label{fig:locality:jax}
     510\end{figure}
     511\begin{figure}
     512        \subfloat[][Throughput share]{
     513                \resizebox{0.5\linewidth}{!}{
     514                        \input{result.locality.share.nasus.ops.pstex_t}
     515                }
     516                \label{fig:locality:nasus:share:ops}
     517        }
     518        \subfloat[][Throughput noshare]{
     519                \resizebox{0.5\linewidth}{!}{
     520                        \input{result.locality.noshare.nasus.ops.pstex_t}
     521                }
     522                \label{fig:locality:nasus:noshare:ops}
     523        }
     524
     525        \subfloat[][Scalability share]{
     526                \resizebox{0.5\linewidth}{!}{
     527                        \input{result.locality.share.nasus.ns.pstex_t}
     528                }
     529                \label{fig:locality:nasus:share:ns}
     530        }
     531        \subfloat[][Scalability noshare]{
     532                \resizebox{0.5\linewidth}{!}{
     533                        \input{result.locality.noshare.nasus.ns.pstex_t}
     534                }
     535                \label{fig:locality:nasus:noshare:ns}
     536        }
     537        \caption[Locality Benchmark on AMD]{Locality Benchmark on AMD\smallskip\newline Throughput and Scalability as a function of \proc count. For Throughput higher is better, for Scalability lower is better. Each series represent 15 independent runs, the dotted lines are extremums while the solid line is the medium.}
     538        \label{fig:locality:nasus}
     539\end{figure}
     540
     541Figure~\ref{fig:locality:jax} and \ref{fig:locality:nasus} shows the results on Intel and AMD respectively.
     542In both cases, the graphs on the left column show the results for the @share@ variation and the graphs on the right column show the results for the @noshare@.
     543
     544On Intel, Figure~\ref{fig:locality:jax} shows Go trailing behind the 3 other runtimes.
     545On the left of the figure showing the results for the shared variation, where \CFA and tokio slightly outperform libfibre as expected.
     546And correspondingly on the right, we see the expected performance inversion where libfibre now outperforms \CFA and tokio.
     547Otherwise the results are similar to the churn benchmark, with lower throughtput due to the array processing.
     548Presumably the reason why Go trails behind are the same as in Figure~\ref{fig:churn:nasus}.
     549
     550Figure~\ref{fig:locality:nasus} shows the same experiment on AMD.
     551\todo{why is cfa slower?}
     552Again, we see the same story, where tokio and libfibre swap places and Go trails behind.
    246553
    247554\section{Transfer}
    248555The last benchmark is more of an experiment than a benchmark.
    249556It tests the behaviour of the schedulers for a misbehaved workload.
    250 In this workload, one of the \gls{at} is selected at random to be the leader.
    251 The leader then spins in a tight loop until it has observed that all other \glspl{at} have acknowledged its leadership.
    252 The leader \gls{at} then picks a new \gls{at} to be the ``spinner'' and the cycle repeats.
    253 The benchmark comes in two flavours for the non-leader \glspl{at}:
     557In this workload, one of the \at is selected at random to be the leader.
     558The leader then spins in a tight loop until it has observed that all other \ats have acknowledged its leadership.
     559The leader \at then picks a new \at to be the next leader and the cycle repeats.
     560The benchmark comes in two flavours for the non-leader \ats:
    254561once they acknowledged the leader, they either block on a semaphore or spin yielding.
    255562
    256563The experiment is designed to evaluate the short-term load-balancing of a scheduler.
    257 Indeed, schedulers where the runnable \glspl{at} are partitioned on the \glspl{proc} may need to balance the \glspl{at} for this experiment to terminate.
    258 This problem occurs because the spinning \gls{at} is effectively preventing the \gls{proc} from running any other \glspl{thrd}.
    259 In the semaphore flavour, the number of runnable \glspl{at} eventually dwindles down to only the leader.
    260 This scenario is a simpler case to handle for schedulers since \glspl{proc} eventually run out of work.
    261 In the yielding flavour, the number of runnable \glspl{at} stays constant.
     564Indeed, schedulers where the runnable \ats are partitioned on the \procs may need to balance the \ats for this experiment to terminate.
     565This problem occurs because the spinning \at is effectively preventing the \proc from running any other \at.
     566In the semaphore flavour, the number of runnable \ats eventually dwindles down to only the leader.
     567This scenario is a simpler case to handle for schedulers since \procs eventually run out of work.
     568In the yielding flavour, the number of runnable \ats stays constant.
    262569This scenario is a harder case to handle because corrective measures must be taken even when work is available.
    263570Note, runtime systems with preemption circumvent this problem by forcing the spinner to yield.
    264571
    265 \todo{code, setup, results}
     572In both flavours, the experiment effectively measures how long it takes for all \ats to run once after a given synchronization point.
     573In an ideal scenario where the scheduler is strictly FIFO, every thread would run once after the synchronization and therefore the delay between leaders would be given by:
     574$ \frac{CSL + SL}{NP - 1}$, where $CSL$ is the context switch latency, $SL$ is the cost for enqueuing and dequeuing a \at and $NP$ is the number of \procs.
     575However, if the scheduler allows \ats to run many times before other \ats are able to run once, this delay will increase.
     576The semaphore version is an approximation of the strictly FIFO scheduling, where none of the \ats \emph{attempt} to run more than once.
     577The benchmark effectively provides the fairness guarantee in this case.
     578In the yielding version however, the benchmark provides no such guarantee, which means the scheduler has full responsability and any unfairness will be measurable.
     579
     580While this is a fairly artificial scenario, it requires only a few simple pieces.
     581The yielding version of this simply creates a scenario where a \at runs uninterrupted in a saturated system, and starvation has an easily measured impact.
     582However, \emph{any} \at that runs uninterrupted for a significant period of time in a saturated system could lead to this kind of starvation.
    266583
    267584\begin{figure}
    … …  
    273590                return
    274591        }
    275 
    276592        // Wait for everyone to acknowledge my leadership
    277593        start: = timeNow()
    … …  
    282598                }
    283599        }
    284 
    285600        // pick next leader
    286601        leader := threads[ prng() % len(threads) ]
    287 
    288602        // wake every one
    289603        if ! exhaust {
    … …  
    293607        }
    294608}
    295 
    296609Thread.wait() {
    297610        this.idx_seen := lead_idx
    … …  
    299612        else { yield() }
    300613}
    301 
    302614Thread.main() {
    303615        while !done  {
    … …  
    312624
    313625\subsection{Results}
    314 Figure~\ref{fig:transfer:jax} shows the throughput as a function of \proc count, where each run uses 100 cycles per \proc and 5 \ats per cycle.
    315 
    316 \todo{results discussion}
     626\begin{figure}
     627\begin{centering}
     628\begin{tabular}{r | c c c c | c c c c }
     629Machine   &                     \multicolumn{4}{c |}{Intel}                &          \multicolumn{4}{c}{AMD}                    \\
     630Variation & \multicolumn{2}{c}{Park} & \multicolumn{2}{c |}{Yield} & \multicolumn{2}{c}{Park} & \multicolumn{2}{c}{Yield} \\
     631\procs    &      2      &      192   &      2      &      192      &      2      &      256   &      2      &      256    \\
     632\hline
     633\CFA      & 106 $\mu$s  & ~19.9 ms   & 68.4 $\mu$s & ~1.2 ms       & 174 $\mu$s  & ~28.4 ms   & 78.8~~$\mu$s& ~~1.21 ms   \\
     634libfibre  & 127 $\mu$s  & ~33.5 ms   & DNC         & DNC           & 156 $\mu$s  & ~36.7 ms   & DNC         & DNC         \\
     635Go        & 106 $\mu$s  & ~64.0 ms   & 24.6 ms     & 74.3 ms       & 271 $\mu$s  & 121.6 ms   & ~~1.21~ms   & 117.4 ms    \\
     636tokio     & 289 $\mu$s  & 180.6 ms   & DNC         & DNC           & 157 $\mu$s  & 111.0 ms   & DNC         & DNC
     637\end{tabular}
     638\end{centering}
     639\caption[Transfer Benchmark on Intel and AMD]{Transfer Benchmark on Intel and AMD\smallskip\newline Average measurement of how long it takes for all \ats to acknowledge the leader \at. DNC stands for ``did not complete'', meaning that after 5 seconds of a new leader being decided, some \ats still had not acknowledged the new leader. }
     640\label{fig:transfer:res}
     641\end{figure}
     642Figure~\ref{fig:transfer:res} shows the result for the transfer benchmark with 2 \procs and all \procs, where each experiement runs 100 \at per \proc.
     643Note that the results here are only meaningful as a coarse measurement of fairness, beyond which small cost differences in the runtime and concurrent primitives begin to matter.
     644As such, data points that are the on the same order of magnitude as eachother should be basically considered equal.
     645The takeaway of this experiement is the presence of very large differences.
     646The semaphore variation is denoted ``Park'', where the number of \ats dwindles down as the new leader is acknowledged.
     647The yielding variation is denoted ``Yield''.
     648The experiement was only run for the extremums of the number of cores since the scaling per core behaves like previous experiements.
     649This experiments clearly demonstrate that while the other runtimes achieve similar performance in previous benchmarks, here \CFA achieves significantly better fairness.
     650The semaphore variation serves as a control group, where all runtimes are expected to transfer leadership fairly quickly.
     651Since \ats block after acknowledging the leader, this experiment effectively measures how quickly \procs can steal \ats from the \proc running leader.
     652Figure~\ref{fig:transfer:res} shows that while Go and Tokio are slower, all runtime achieve decent latency.
     653However, the yielding variation shows an entirely different picture.
     654Since libfibre and tokio have a traditional work-stealing scheduler, \procs that have \ats on their local queues will never steal from other \procs.
     655The result is that the experiement simply does not complete for these runtime.
     656Without \procs stealing from the \proc running the leader, the experiment will simply never terminate.
     657Go manages to complete the experiement because it adds preemption on top of classic work-stealing.
     658However, since preemption is fairly costly it achieves significantly worst performance.
     659In contrast, \CFA achieves equivalent performance in both variations, demonstrating very good fairness.
     660Interestingly \CFA achieves better delays in the yielding version than the semaphore version, however, that is likely due to fairness being equivalent but removing the cost of the semaphores and idle-sleep.
Note: See TracChangeset for help on using the changeset viewer.