Ignore:
Timestamp:
Apr 13, 2026, 3:05:44 AM (2 weeks ago)
Author:
Michael Brooks <mlbrooks@…>
Branches:
master
Children:
5b21636b
Parents:
2581f1e
Message:

Add overlaid means to list perf histograms. Add 2nd-order graph to the paper and its discussion.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/theses/mike_brooks_MMath/list.tex

    r2581f1e r1abcec9b  
    10341034  \includegraphics{plot-list-1ord.pdf}
    10351035  \caption{Histogram of operation durations, decomposed by all first-order effects.
    1036   Each of the three breakdowns divides the entire population of test results into its mutually disjoint constituents.
    1037   \MLB{missing: overlay of means}}
     1036  Each of the three breakdowns divides the entire population of test results into its mutually disjoint constituents.}
    10381037  \label{fig:plot-list-1ord}
    10391038\end{figure}
     
    10461045
    10471046A similar situation comes from \VRef[Figure]{fig:plot-list-1ord}'s second comparison, by operation type.
    1048 Specific interactions like framework X doing better on stacks do occur; a selection of them is addressed in \MLB{TODO: cross reference}.
     1047Specific interactions do occur, like framework X doing better on stacks than on queues; a selection of these is addressed in \VRef[Figure]{fig:plot-list-2ord} and discussed shortly.
    10491048But they are so irrelevant to the issue of picking a winning framework that it is sufficient here to number the operations opaquely.
    10501049Whether a given list implementation is suitable for a language's general library succeeds or fails without knowledge of whether your use will have stack or queue movement.
     
    10601059As does a small size on the Intel typically beat a medium size on the AMD by 66\%.
    10611060Framework choice is simply not where you stand to win or lose the most.
     1061
     1062\begin{figure}
     1063        \centering
     1064        \includegraphics{plot-list-2ord.pdf}
     1065        \caption{Histogram of operation durations, illustrating interactions with framework.
     1066        Each distribution shows how its framework reacts to a single other factor being varied across one pair of options.
     1067        Every (binned and mean-contributing) individual data point represents a pair of test setups, one with the criterion set to the option labelled at the top; the other setup uses the bottom option.
     1068        This point's y-axis score is the ratio of these setups' durations.
     1069        The point lands in a bin closer to the label of the option that performs better.
     1070        }
     1071        \label{fig:plot-list-2ord}
     1072\end{figure} 
     1073
     1074\VRef[Figure]{fig:plot-list-1ord} stays razor-focused on only first-order effects in order to contextualize a winner/loser framework observation.
     1075But this perspective cannot address questions like, ``Where are \CFA's sore spots?''
     1076Moreover, the shallow threatment of operations by ordinals said nothing about how stack usage compares with queues'.
     1077
     1078\VRef[Figure]{fig:plot-list-2ord} provides such answers.
     1079Its size-zone criterion refines the obvious notion that a small size runs faster than a big size; this issue is by how much.
     1080Indeed, all means favour small and few tails favour medium.
     1081But the various frameworks do no respond to the different sizes and machines uniformly.
     1082On the AMD, \CFA and \uCpp have a modest size sensitivity, LQ-tailq's is moderate amd LQ-list seems unaffected.
     1083On the Intel, \CFA's increases to moderate, while \uCpp is now unaffected, and both LQs have a dramatic response.
     1084The Intel is more sensitive to size than the AMD.
     1085
     1086Turning next to movement and polarity, the responses appear more subdued.
     1087Note that LQ-list has no represntation in these comparisons because it only supports stacks that push and pop with the first element.
     1088\CFA is completely stable under movement and polarity changes.
     1089\uCpp and LQ show modest responses favouring queues and insertion at last.
     1090
     1091Finally, with accessor, a \CFA sore spot emerges.
     1092Note the pair of two-way comparisons pulled from the three experiment setups used.
     1093First, the all-head/insert-element opposition addresses which insertion style is better---by-head (top) and by-element (bottom).
     1094Then, the all-head/remove-element opposition addresses which removal style is better---by-head (top) and by-element (bottom).
     1095The LQs favour insertion by head and removal by element.
     1096\CFA and \uCpp favour both operations by head.
     1097The strongest effect is \CFA's aversion to removal by element---certainly an opportunity for improvement.
     1098
     1099\begin{comment}
     1100        These remarks are mostly about 3ord over 2ord.
     1101This analysis does not provide more detail about one framework beating another; it offers different benefits.
     1102These interactions further illustrate the lottery-ticket unpredictability that a linked-list user inevitably faces, by revealing stronger-still performance swings hidden from the first-order view.
     1103They illustrate the difficult signal-to-noise ratio that I had to overcome in preparing this data.
     1104They may serve as a reference guiding future \CFA linked-list work by informing on where to target improvements.
     1105Finally, the findings offer the conclusion that \CFA's list offers more consostent performance across usage scenarios, than the other lists.
     1106\end{comment}
     1107
     1108\begin{comment}
     1109Further to the interpretation guidance of \VRef[Figure]{fig:plot-list-2ord}'s caption, a comparison with the construction of \VRef[Figure]{fig:plot-list-1ord} may be helpful.
     1110In the first-order graph, the factors being compared had many options: four, twelve and four.
     1111# XXX Each option contributes its own, seemingly independent, mean and distribution.
     1112# XXX But, in fact, they are not totally independent.
     1113# WRONG: it's not just about binary, you also need a split on a conditioned factor
     1114        I'm trying to get to:
     1115Side by side in earlier style, but they're opposites, so they mirror each other, so you take option B, flip it over, and have option A---I'll just show A
     1116\end{comment}
     1117
     1118
    10621119
    10631120\MLB{ TODO: find a home for these original conclusions:
     
    11241181  \caption{Histogram of operation durations, decomposed by physical factors.
    11251182  Measurements are included from only the sizes in the ``small'' and ``medium'' stable zones.
    1126   This breakdown divides the entire population of test results into four mutually disjoint constituents.}
     1183  This breakdown divides the entire population of test results into four mutually disjoint constituents.
     1184  \MLB{I see that I broke it. But we might be getting rid of it.}
     1185  }
    11271186  \label{fig:plot-list-mchn-szz}
    11281187\end{figure}
     
    11311190Each of these four histograms shows variation in duration coming from the four specific sizes in a size zone, from combining results of all twelve operations and all four frameworks.
    11321191Among the means of the four histograms, there is a standard deviation of 0.9 ns, which is 20\% of the global mean.
    1133 This variability is due solely to physial factors.
     1192This variability is due solely to physical factors.
    11341193
    11351194From the perspective of assessing winning/losing frameworks, these physical effects are noise.
Note: See TracChangeset for help on using the changeset viewer.