Ignore:
Timestamp:
Apr 10, 2026, 9:50:22 AM (3 weeks ago)
Author:
Michael Brooks <mlbrooks@…>
Branches:
master
Children:
806534c
Parents:
6767f27
Message:

Revise presentation of absolute times and add discussion of their physical influences.

File:
1 edited

Legend:

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

    r6767f27 r17f2a7f4  
    955955
    956956The preceding result shows that all the intrusive implementations examined have noteworthy performance compared to wrapped lists.
    957 This analysis picks the list region 10-150 and zooms-in to differentiate among the different intrusive implementations.
     957This analysis picks the sizes below 150 and zooms in to differentiate among the different intrusive implementations.
    958958The data is selected from the start of \VRef[Figure]{f:Linear}, but the start of \VRef[Figure]{f:Shuffled} would be largely the same.
    959959
     
    963963  \begin{tabular}{p{0.75in}p{2.75in}p{3in}}
    964964  &
    965   \subfloat[Absolute Time, AMD]{\label{f:AbsoluteTime-swift}
     965  \subfloat[Operation I, AMD]{\label{f:AbsoluteTime-i-swift}
    966966        \hspace*{-0.75in}
    967         \includegraphics{plot-list-zoomin-abs-swift.pdf}
     967        \includegraphics{plot-list-zoomin-abs-i-swift.pdf}
    968968  } % subfigure
    969969  &
    970   \subfloat[Absolute Time, Intel]{\label{f:AbsoluteTime-java}
    971         \includegraphics{plot-list-zoomin-abs-java.pdf}
     970  \subfloat[Operation I, Intel]{\label{f:AbsoluteTime-i-java}
     971        \includegraphics{plot-list-zoomin-abs-i-java.pdf}
    972972  } % subfigure
    973973  \\
    974974  &
    975   \subfloat[Relative Time, AMD]{\label{f:RelativeTime-swift}
     975  \subfloat[Operation VIII, AMD]{\label{f:AbsoluteTime-viii-swift}
    976976        \hspace*{-0.75in}
    977         \includegraphics{plot-list-zoomin-rel-swift.pdf}
     977        \includegraphics{plot-list-zoomin-abs-viii-swift.pdf}
    978978  } % subfigure
    979979  &
    980   \subfloat[Relative Time, Intel]{\label{f:RelativeTime-java}
    981         \includegraphics{plot-list-zoomin-rel-java.pdf}
     980  \subfloat[Operation VIII, Intel]{\label{f:AbsoluteTime-viii-java}
     981        \includegraphics{plot-list-zoomin-abs-viii-java.pdf}
    982982  } % subfigure
    983983  \end{tabular}
    984   \caption{Operation duration \vs list length at small-medium lengths.  One example operation is shown: stack movement, insert-first polarity and head-mediated access.  (a) has absolute times.  (b) has times relative to those of LQ-\lstinline{tailq}.}
     984  \caption{Operation duration \vs list length at small-medium lengths.  Two example operations are shown: [I] stack movement with head-only access (plots a and b); [VIII] queue movement with element-oriented removal access (plots c and d); both operations use insert-first polarity.}
    985985  \label{fig:plot-list-zoomin}
    986986\end{figure}
    987987
    988 \VRef[Figure]{fig:plot-list-zoomin} shows the zone from 10--150 blown up, both in absolute and relative time.
     988\VRef[Figure]{fig:plot-list-zoomin} shows the sizes below 150 blown up.
    989989% The same scenario as the coarse comparison is used: a stack, with insertions and removals happening at the end called ``first,'' ``head'' or ``front,'' and all changes occurring through a head-provided insert/remove operation.
    990990The error bars show fastest and slowest time seen on five trials, and the central point is the mean of the remaining three trials.
    991991For readability, the points are slightly staggered at a given horizontal value, where the points might otherwise appear on top of each other.
    992992
     993\VRef[Figure]{fig:plot-list-zoomin} has the pair machines, each in a column.
     994It also has a pair of operating scenarios, each in a row.
     995The experiment runs twelve operating scenarios; the ones chosen for their variety happen to be items I and VIII from the listing of \MLB{TODO: cross reference}.
     996Note that LQ-list does not support queue operations, so this framework is absent from Operation VIII.
     997
     998At lengths 1 and 2, winner patterns seen at larger sizes generally do not apply.
     999Indeed, an issue with \CFA giving terribel on queues at length 1 is evident in \VRef[Figure]{f:AbsoluteTime-viii-swift}.
     1000This phenomenon is elaborated in \MLB{TODO: xref}.
     1001For the remainder of this section, these sizes are disregarded.
     1002
     1003Even after the very-small anomalies, the selections of operation and machine significantly affect how speed responds to size.
     1004For example, Operation I on the AMD (\VRef[Figure]{f:AbsoluteTime-i-swift}) has \CFA generally winning over LQ, while the opposite is seen by switching either to Operation VIII (\VRef[Figure]{f:AbsoluteTime-viii-swift}) or to the Intel (\VRef[Figure]{f:AbsoluteTime-i-java}).
     1005For another, Operation I has sore spots at lengths in the middle for \uCpp on AMD and LQ-list on Intel, which resolve at larger lengths; yet no such pattern presents with Operation VIII.
     1006
     1007In spite of these complex interactions, a couple spots of stability can be analyzed.
     1008In these examples, the size zones 4--16, ``small,'' and above 48, ``medium,'' covering four specific sizes apiece, each tends to show a simple winner/loser story.
     1009Manual inspection of other such plots (not detailed) showed that this quality is generally upheld.
     1010So these zones are used for basing comparison.
     1011
     1012\begin{figure}
     1013  \centering
     1014  \includegraphics{plot-list-mchn-szz.pdf}
     1015  \caption{Histogram of operation durations, decomposed by physical factos.
     1016  Measurements are included from only the sizes in the ``small'' and ``medium'' stable zones.}
     1017  \label{fig:plot-list-mchn-szz}
     1018\end{figure}
     1019
     1020\VRef[Figure]{fig:plot-list-mchn-szz} shows the effects of the physical factors of size zone and machine.
     1021Each 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.
     1022Among the means of the four histograms, there is a standard deviation of 0.9 ns, which is 20\% of the global mean.
     1023This variability is due solely to physial factors.
     1024
     1025From the perspective of assessing winning/losing frameworks, these physical effects are noise.
     1026So, subsequent analysis conditions on the phisical effects.
     1027That is, it presents results relative to the mean of the physical quadrant (\VRef[fig]{fig:plot-list-mchn-szz} histogram) to which it belogs.
     1028With this adjustment, absolute duration values (in nonsecods) are lost.
     1029In return, the physical quadrants are re-combined, enabling assessment of the non-physical factors.
     1030
     1031\MLB{Peter, stop here.  Graph and discussion of these non-physical factos is coming.}
     1032
     1033\begin{comment}
    9931034While preparing experiment results, I first tested on my old office PC, AMD FX-8370E Eight-Core, before switching to the large new server for final testing.
    9941035For this experiment, the results flipped in my favour when running on the server.
     
    10031044@tailq@'s mean is always zero by definition, but its error bars, representing a single scenario's re-run stability, are still meaningful.
    10041045With this bend straightened out, aggregating across lengths is feasible.
     1046\end{comment}
    10051047
    10061048\begin{figure}
Note: See TracChangeset for help on using the changeset viewer.