|
|
@@ -251,12 +251,32 @@ Hekaton utilizes optimistic multi-version concurrency control (MVCC), it mainly
|
|
|
\end{frame}
|
|
|
|
|
|
\begin{frame}
|
|
|
-\frametitle{Template}
|
|
|
+\frametitle{Benchmarks}
|
|
|
+The authors utilized two types of benchmarks:
|
|
|
+\begin{itemize}
|
|
|
+ \item \textbf{YCSB Benchmark} (50GB single-table database, 1KB records) that is divided in:
|
|
|
+ \begin{itemize}
|
|
|
+ \item Read-heavy: 90\% reads and \% updates.
|
|
|
+ \item Write-heavy: 50\% reads and 50\% writes.
|
|
|
+ \item Read-only: 100\5 reads.
|
|
|
+ \end{itemize}
|
|
|
+ \item \textbf{Multi-step read/update workload} (1GB single-table database, 56 bytes records) that is divided in:
|
|
|
+ \begin{itemize}
|
|
|
+ \item Read-only.
|
|
|
+ \item Update-only.
|
|
|
+ \end{itemize}
|
|
|
+\end{itemize}
|
|
|
\end{frame}
|
|
|
|
|
|
|
|
|
\begin{frame}
|
|
|
-\frametitle{Template}
|
|
|
+\frametitle{In-Memory Cold storage}
|
|
|
+These analysis is done in order to isolate the overhead caused by only the Siberia framework, eliminating the time due to I/O operations.
|
|
|
+\begin{figure}
|
|
|
+\caption{In-memory overhead of the Siberia framework.}
|
|
|
+\centering
|
|
|
+\includegraphics[width=0.7\textwidth,height=0.60\textheight]{in-memory-overhead}
|
|
|
+\end{figure}
|
|
|
\end{frame}
|
|
|
|
|
|
|
