diff options
Diffstat (limited to 'main.tex')
| -rw-r--r-- | main.tex | 34 |
1 files changed, 19 insertions, 15 deletions
@@ -92,23 +92,30 @@ \end{frame} \begin{frame}\frametitle{\textbf{RQ2}: Reference Architecture} + % Make Kafka logos clearly defined --> add a legend with icons? + \hspace{-0.3cm} \begin{minipage}[b]{0.45\linewidth} - \begin{tcolorbox}[title=Implementation] - %Add the _implementation_ figure here instead. - % I.e., the Kafka, the broker, PostgreSQL, Redis. - % In the implementation graph: keep the datacenter "just" a datacenter -- don't yet mention we use OpenDC. - % Make Kafka logos clearly defined --> add a legend with icons? - \end{tcolorbox} - \vspace{1cm} + \begin{center} + % Change to Datacenter (Physical Twin) + \includegraphics[width=1.15\textwidth]{images/ref_architecture.pdf} + \end{center} + \vspace{-0.2cm} + \tiny + \textbf{Figure 1.4:} The predictive datacenter digital twin reference architecture. + The architecture was designed with the \emph{AtLarge Design Process}~\cite{DBLP:conf/icdcs/IosupVTETBFMT19}. + \vspace{0.2cm} \end{minipage} + \hspace{0.8cm} \begin{minipage}[b]{0.45\linewidth} \begin{center} - % Change to Datacenter (Physical Twin) - \includegraphics[width=1.25\textwidth]{images/ref_architecture.pdf} + \includegraphics[width=1.15\linewidth]{images/implementation.png} \end{center} \vspace{-0.2cm} \tiny - \textbf{Figure 1.4:} The predictive datacenter digital twin reference architecture. \end{minipage} + \textbf{Figure 1.5:} The prototype based on \textbf{Figure 1.4} towards answering \textbf{RQ3}. + The time-series data flows first to the \texttt{Grafana} dashboard, \texttt{PostgreSQL} database and \texttt{Redis} cache, as advised in~\cite{DBLP:conf/sc/TaheriBPRHDEWPM24}. + \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. @@ -116,13 +123,10 @@ \end{frame} % You should skip \hfill completely or in favour of \hspace very minimally. \begin{frame}\frametitle{\textbf{RQ3}: Experimental Setup} - % The software stack of \emph{Sunfish} includes state-of-the-art software. - %The time-series data flows first to the \texttt{Grafana} dashboard, \texttt{PostgreSQL} database and \texttt{Redis} cache, as advised in~\cite{DBLP:conf/sc/TaheriBPRHDEWPM24}. - \begin{minipage}[b]{0.45\linewidth} \begin{tcolorbox}[title=Problem, colbacktitle=red!70!black,colback=red!20!white] We cannot just go and test digital twins on large systems, because we do not have large systems at hand. - Moreover, real-world experimentation is costly and unsustainable in the long run~\cite{DBLP:conf/ccgrid/MastenbroekAJLB21}. + Moreover, real-world experimentation is costly and unsustainable in the long run~\cite{DBLP:conf/ccgrid/MastenbroekAJLB21}. \end{tcolorbox} \vspace{0.5cm} \begin{tcolorbox}[title=Solution, colbacktitle=Green!70!black, colback=Green!20!white] @@ -140,7 +144,7 @@ \end{center} \tiny \vspace{-0.2cm} - \textbf{Figure 1.5:} The experimental setup. + \textbf{Figure 1.6:} The experimental setup. Answering \textbf{RQ3} we provide a novel way to evaluate datacenter digital twins through discrete-event simulation. \end{minipage} \end{frame} |