summaryrefslogtreecommitdiff
path: root/main.tex
diff options
context:
space:
mode:
Diffstat (limited to 'main.tex')
-rw-r--r--main.tex97
1 files changed, 60 insertions, 37 deletions
diff --git a/main.tex b/main.tex
index 1a7d4a7..051d295 100644
--- a/main.tex
+++ b/main.tex
@@ -2,11 +2,11 @@
\input{style/style.tex}
\begin{document}
-\frame{\titlepage \centering \footnotesize Online slides: \url{https://www.overleaf.com/read/tknhxmqfgtdy\#87413e}}
+\frame{\titlepage \centering \footnotesize Online slideshow: \url{mjkw.pl/vu/bsc}}
\begin{frame}\frametitle{Motivation}
\begin{tcolorbox}[title=Context]
- 21\textsuperscript{st} century datacenters are primarily heterogeneous~\cite{DBLP:conf/date/MilojicicFDR21} and
+ 21\textsuperscript{st} century datacenters (DC) are mostly heterogeneous~\cite{DBLP:conf/date/MilojicicFDR21} and
modern computational needs of AI drive managers to diversify datacenters even more~\cite{DBLP:journals/computer/AthavaleBBMMPS24}.
In result datacenters become extremely complex and hard to operate with millions of CPU's, GPU's etc.
\end{tcolorbox}
@@ -57,72 +57,95 @@
\begin{frame}\frametitle{\textbf{RQ1}: Literature Review I}
\begin{tcolorbox}[title=Results]
- This is a dummy sentence meant to make the tcolorbox have more than 2 lines of text width so that I am able to show the text and the table spacing better.
- I hope it fits its purpose well.
+ The literature on DCDTs is scarce.
+ Some systems barely classify as DTs (\emph{e.g.,} Kalibre~\cite{DBLP:conf/sensys/WangZD0TCWZ20}, ChatTwin~\cite{DBLP:conf/sensys/LiW0Z0T23}).
+ Existing deployments specialize in \textcolor{Red}{Cooling and Heat Modelling}, together with \textcolor{Red}{3D visualizations}.
+ Most lack crucial predictive DC behaviour modelling.
\end{tcolorbox}
\input{images/table.tex}
+ % Research on DTs for datacenters have been separate, siloed efforts focused on either datacenter cooling, network performance, power consumption or visualization efforts.
+ % CFD usually means Navier-Stokes equations.
+ % CFD models take ages to compute.
\end{frame}
\begin{frame}\frametitle{\textbf{RQ1}: Literature Review II}
% Mandatory: split the figure into 2: top and bottom, and that way you can fill in the entire slide nicely.
- \begin{tcolorbox}[title=A generic system model]
-
- This is a dummy sentence meant to make the tcolorbox have more than 2 lines of text width so that I am able to show the text and the table spacing better.
+ \begin{tcolorbox}[title=A holistic DCDT system model]
+ We propose a generic model of datacenter digital twinning that can be mapped to each system from \textbf{Table 1.1}. To answer \textbf{RQ2}, we design a ref. arch. for \emph{Operations Model}.
\end{tcolorbox}
\begin{center}
\includegraphics[width=0.8\textwidth]{images/system_model2.pdf}
\end{center}
+ % The reason why the cooling system is in the graph is because of the fact that 40\% of total energy consumed in DCs comes from cooling~\cite{DBLP:conf/noms/ZhangZLZWC22}.
+ % It has come to the point where datacenters are being build in the Pan-Arctic region, such as Finland,Russia,Sweden etc. with Iceland leading in number of DCs https://www.datacentermap.com/iceland/
+ % The SmarDC digital twin is purely to get more training data for AI models.
+ % Not really a digital twin per se.
\tiny
- \textbf{Figure 1.3:} To answer \textbf{RQ1} we designed a generic datacenter digital twin system model based on a comprehensive literature review and findings from \textbf{Table 1.1}.
+ \textbf{Figure 1.3:} To answer \textbf{RQ1} we designed a generic datacenter digital twin system model based on a comprehensive literature review and findings from \textbf{Table 1.1}. The \emph{Infrastructure Model} simulates the structure of the DC and the \emph{Operations model} simulates the behaviour of the DC.
% Consider splitting the figure into 2 a.k.a. top and bottom.
+ % By the AIAA definition, the DT mimicks the structure and behaviour.
% Data Lake -> Data Storage
+ % Use cases of DT's found by Brewer et al.: augmented reality, forensic analysis and diagnostics, predictive modelling, failure detection, operational optimization, ``what-if''' scenarios and virtual prototyping.
\end{frame}
\begin{frame}\frametitle{\textbf{RQ2}: Reference Architecture}
\begin{minipage}[b]{0.45\linewidth}
+ \begin{tcolorbox}[title=Use cases]
+
+ \end{tcolorbox}
+ \vspace{1cm}
+ \end{minipage}
+ \begin{minipage}[b]{0.45\linewidth}
\begin{center}
\includegraphics[width=1.25\textwidth]{images/ref_architecture.pdf}
\end{center}
\vspace{-0.2cm}
\tiny
- \textbf{Figure 1.4:} The predictive datacenter digital twin architecture.
- \end{minipage}
- \hfill
+ \textbf{Figure 1.4:} The predictive datacenter digital twin architecture. \end{minipage}
+ % We decided to use discrete-event simulation, as opposed to computational fluid dynamics because of the high overheads of development time needed for CFD.
+ % CFD simply takes too long to run, making it unfeasible for real-time analytics and simulation.
+ % Citing ExaDigit: [CFD] they are also more computationally expensive, generally making real-time operation unfeasible.
% Consider adding this minipage directly to the ``draw.io'' diagram
- \begin{minipage}[b]{0.42\linewidth}
- \footnotesize
- \textbf{Functional Requirements}
- \tiny
-
- \textbf{FR1:} The system shall be able to
-
- \textbf{FR2:} The system should be able to
-
- \textbf{FR3:} The system needs to do this and that
+\end{frame}
- \vspace{1cm}
- \footnotesize
- \textbf{Non-functional Requirements}
+\begin{frame}\frametitle{\textbf{RQ3}: Experimental Setup}
+ \begin{minipage}[b]{0.45\linewidth}
+ \begin{center}
+ \includegraphics[width=1.2\linewidth]{images/predictive_analyticsv2.pdf}
+ \end{center}
+ \vspace{-0.3cm}
\tiny
-
- \textbf{NFR1:} The system shall be able to
-
- \textbf{NFR2:} The system should be able to
-
- \textbf{NFR3:} The system needs to do this and that
-
- \vspace{3cm}
+ \textbf{Figure 1.5:} Evaluating DCDTs is difficult. To answer \textbf{RQ3} we provide a novel way to evaluate datacenter digital twins through discrete-event simulation.
+ \end{minipage}
+ \hfill
+ \begin{minipage}[b]{0.45\linewidth}
+ \begin{center}
+ \includegraphics[width=0.7\linewidth]{images/scrs.jpg}
+ \end{center}
+ \vspace{-0.2cm}
+ \tiny
+ \textbf{Figure 1.6:} The software stack used to implement \emph{Sunfish}.
+ The time-series data flows initially to the \texttt{Grafana} dashboard, \texttt{PostgreSQL} database and \texttt{Redis} cache, as suggested in~\cite{DBLP:conf/sc/TaheriBPRHDEWPM24}.
\end{minipage}
\end{frame}
\begin{frame}\frametitle{\textbf{RQ3}: Experimental Results I}
\begin{tcolorbox}[title=Main Finding I]
- Here explain what did you find.
+ On average, \emph{Sunfish} achieves 12.17\% less failures per task than baseline (OpenDC).
+ Insights from predictive digital twinning yield noticeable performance difference.
\end{tcolorbox}
- Here goes the figure that backs up claim in Main Finding I.
- Evidence for Main Finding I.
+ \begin{minipage}[b]{0.45\linewidth}
+ \begin{center}
+ \includegraphics[width=1.1\textwidth]{images/18_Jun_2026_201008.pdf}
+ \end{center}
+ \vspace{-0.3cm}
+ \tiny
+ \textbf{Figure 1.5:} Experiment 1 -- on the \emph{x}-axis are different community failure traces.
+ On the \emph{y}-axis is the mean number of times a task has failed, during the entire workload.
+ Vertical bars is standard deviation, measured over 5 repetitions.
+ \end{minipage}
% Explain what the axis are in the figure caption.
% Talk about the experimental setup in the figure.
% Give more reliable results than just numbers -- do statistical testing, i.e., standard deviation, confidence intervals.
@@ -133,7 +156,7 @@
\begin{tcolorbox}[title=Main Finding II]
Here explain what did you find.
\end{tcolorbox}
- Here goes the figure that backs up claim in Main Finding II.
+
\end{frame}
\begin{frame}\frametitle{Key Takeaways}
@@ -159,7 +182,7 @@
\end{frame}
-\setcounter{framenumber}{3}
+\setcounter{framenumber}{4}
\setbeamertemplate{footline}[page number]{
% Unfortunately this must remain here.