aboutsummaryrefslogtreecommitdiff
path: root/thesis/parts
diff options
context:
space:
mode:
authorAria Shrimpton <me@aria.rip>2024-03-25 18:54:08 +0000
committerAria Shrimpton <me@aria.rip>2024-03-25 18:54:08 +0000
commite2d0806b2d944b87eb2a00bb46243a1d50487a3e (patch)
tree1096059e340ba64d6186fde7dc8810f9e7c2cb26 /thesis/parts
parent57c3c48f6660f905fb974cff7ec58f746a1a6970 (diff)
update data & analysis
Diffstat (limited to 'thesis/parts')
-rw-r--r--thesis/parts/results.tex44
1 files changed, 19 insertions, 25 deletions
diff --git a/thesis/parts/results.tex b/thesis/parts/results.tex
index dbc8b14..2f06d06 100644
--- a/thesis/parts/results.tex
+++ b/thesis/parts/results.tex
@@ -21,10 +21,8 @@ To help readability, we group these into regular \code{Container} implementation
\begin{figure}[h!]
\centering
- \includegraphics[width=10cm]{assets/insert_containers.png}
- \par\centering\rule{11cm}{0.5pt}
- \includegraphics[width=10cm]{assets/insert_mappings.png}
- \caption{Estimated cost of insert operation on \code{Container} implementations and \code{Mapping} implementations}
+ \includegraphics[width=10cm]{assets/insert.png}
+ \caption{Estimated cost of insert operation by implementation}
\label{fig:cm_insert}
\end{figure}
@@ -65,12 +63,8 @@ This is desirable assuming that \code{contains} operations are actually randomly
\begin{figure}[h!]
\centering
- \includegraphics[width=10cm]{assets/contains_lists.png}
- \par\centering\rule{11cm}{0.5pt}
- \includegraphics[width=10cm]{assets/contains_sets.png}
- \par\centering\rule{11cm}{0.5pt}
- \includegraphics[width=10cm]{assets/contains_mappings.png}
- \caption{Estimated cost of \code{contains} operation on lists, sets/sorted lists, and \code{Mapping}s}
+ \includegraphics[width=10cm]{assets/contains.png}
+ \caption{Estimated cost of \code{contains} operation by implementation}
\label{fig:cm_contains}
\end{figure}
@@ -177,21 +171,21 @@ In all but two of our test cases (marked with *), we correctly identify the best
\begin{table}[h!]
\centering
- \begin{tabular}{c|c|c|c|c|}
- & Project & Container Type & Actual Best & Predicted Best \\
- \hline
- & aoc\_2021\_09 & Map & HashMap & HashMap \\
- & aoc\_2021\_09 & Set & HashSet & HashSet \\
- & aoc\_2022\_14 & Set & HashSet & HashSet \\
- * & aoc\_2022\_14 & List & Vec & LinkedList \\
- & example\_stack & StackCon & Vec & Vec \\
- & example\_sets & Set & HashSet & HashSet \\
- & example\_mapping & Map & HashMap & HashMap \\
- & aoc\_2022\_08 & Map & HashMap & HashMap \\
- * & prime\_sieve & Primes & BTreeSet & HashSet \\
- & prime\_sieve & Sieve & Vec & Vec \\
- & aoc\_2022\_09 & Set & HashSet & HashSet \\
- \end{tabular}
+\begin{tabular}{|c|c|c|c|}
+Project & Container Type & Best implementation & Predicted best \\
+\hline
+aoc\_2022\_09 & Set & HashSet & HashSet \\
+example\_stack & StackCon & Vec & Vec \\
+aoc\_2021\_09 & Set & HashSet & HashSet \\
+aoc\_2021\_09 & Map & HashMap & HashMap \\
+aoc\_2022\_14 & Set & HashSet & HashSet \\
+aoc\_2022\_14 & List & Vec & LinkedList \\
+aoc\_2022\_08 & Map & HashMap & HashMap \\
+example\_sets & Set & HashSet & HashSet \\
+example\_mapping & Map & HashMap & HashMap \\
+prime\_sieve & Primes & HashSet & BTreeSet \\
+prime\_sieve & Sieve & Vec & LinkedList \\
+\end{tabular}
\caption{Actual best vs predicted best implementations}
\label{table:predicted_actual}
\end{table}