Minor corrections to Testing Arrangements in 4.3.1 and 5.4.4
This commit is contained in:
parent
39a80f972f
commit
3709cc115b
@ -103,12 +103,12 @@ All nodes are connected with a 10Gbps Infiniband interconnect.
|
||||
\TUsubsection{Experimental Networks} \label{sec:Sync-Test}
|
||||
The example networks for testing the effectiveness of synchronous firing follow the compliance graph generation approach. These networks analyze two assets, both of which are identical 2006 Toyota Corolla cars with identical qualities. The generation examines both cars at their current states, and proceeds to advance in time by a pre-determined amount, up to a pre-determined limit. Each time increment updates each car by an identical amount of mileage. During the generation process, it is determined if a car is out of compliance either through mileage or time since its last maintenance in accordance with the Toyota Corolla Maintenance Schedule manual.
|
||||
|
||||
In addition, the tests employ the use of ``services", where if a car is out of compliance, it will go through a correction process and reset the mileage and time since last service. Each test varies in the number of services used. The 1 Service test only employs one service, and it is dedicated to brake pads. The 2 Service test employs two services, where the first service is dedicated to the brake pads, and the second is for exhaust pipes. This process extends to the 3 and 4 Service tests.
|
||||
In addition, the tests employ the use of ``services", where if a car is out of compliance, it will go through a correction process and reset the mileage and time since last service. Each test varies in the number of services used. The 1 Service test only employs one service, and it is dedicated to brake pads. The 2 Service test employs two services, where the first service is dedicated to the brake pads, and the second is for exhaust pipes. This process extends to the 3, 4, 5, and 6 Service tests.
|
||||
The testing information is as follows:
|
||||
\begin{itemize}
|
||||
\item{All tests ran for 12 months, with time steps of 1 month.}
|
||||
\item{All tests had the same number of compliance checks: brake pads, exhaust pipes, vacuum pumps, and AC filters.}
|
||||
\item{There were 10 base exploits, and an additional 4 exploits were individually added in the form of services for each test.}
|
||||
\item{All tests had the same number of compliance checks: brake pads, exhaust pipes, vacuum pumps, AC filters, oil changes, and driveshaft boots.}
|
||||
\item{There were 12 base exploits, and an additional 6 exploits were individually added in the form of services for each test.}
|
||||
\item{All tests used the same network model.}
|
||||
\item{All tests used the same exploit file, with the exception of the ``group" keyword being present in the synchronous firing testing.}
|
||||
\item{Services must be performed prior to advancing time, if services are applicable.}
|
||||
|
||||
@ -62,11 +62,11 @@
|
||||
\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.4.2.4}MPI Tags}{46}{}\protected@file@percent }
|
||||
\@writefile{toc}{\contentsline {subsection}{\numberline {5.4.3}\it Performance Expectations and Use Cases}{46}{}\protected@file@percent }
|
||||
\newlabel{sec:perf_expec_subg}{{5.4.3}{46}}
|
||||
\citation{lawrence_livermore_national_laboratory_mpip_nodate}
|
||||
\@writefile{lot}{\contentsline {table}{\numberline {5.2}{\ignorespaces MPI Tags for the MPI Subgraphing Approach\relax }}{47}{}\protected@file@percent }
|
||||
\newlabel{table:subg-tag}{{5.2}{47}}
|
||||
\@writefile{toc}{\contentsline {subsection}{\numberline {5.4.4}\it Results}{47}{}\protected@file@percent }
|
||||
\newlabel{sec:Subgraphing-Results}{{5.4.4}{47}}
|
||||
\citation{lawrence_livermore_national_laboratory_mpip_nodate}
|
||||
\@writefile{lof}{\contentsline {figure}{\numberline {5.13}{\ignorespaces First iteration results of MPI Subgraphing in terms of Runtime\relax }}{48}{}\protected@file@percent }
|
||||
\newlabel{fig:Subg_base}{{5.13}{48}}
|
||||
\@writefile{lof}{\contentsline {figure}{\numberline {5.14}{\ignorespaces First iteration results of MPI Subgraphing in terms of Speedup and Efficiency\relax }}{49}{}\protected@file@percent }
|
||||
|
||||
12
Chapter5.tex
12
Chapter5.tex
@ -238,7 +238,17 @@ Similar to Section \ref{sec:tasking-tag} that discussed the usage of MPI Tags fo
|
||||
This approach is intended to reduce runtime when the frontier grows at a rate faster than it can be explored. However, since this approach is designed for distributed systems, there is no guarantee that speedup can be achieved when duplicate work is performed. Not only is there wasted time by the worker nodes when duplicate work occurs, but duplicate work also contributes to increased communication between nodes to adequately explore the graph, and also leads to an increased number of merging calls by the root node. The ideal scenario for the subgraphing approach is when the graph is sparse, and the graph aligns more with a N-Ary tree structure where each node only has one parent. When the graph is sparse, there is a lower likelihood of duplicate work occurring, since worker nodes have a lower probability of exploring a graph state that connects to a different graph state that has been (or will be) explored by another worker node. If each graph state was able to have only one parent, there is a lower likelihood that worker nodes would explore the same graph cluster.
|
||||
|
||||
\TUsubsection{Results} \label{sec:Subgraphing-Results}
|
||||
A series of tests were conducted on the platform described at the beginning of Section \ref{sec:test-platform}, and results were collected in regards to the effect of the MPI Subgraphing approach on the 4 example networks discussed in \ref{sec:Sync-Test}. All tests used synchronous firing. Figure \ref{fig:Subg_base} shows the runtimes of each of the test cases. Only the serial runtime from the 2 Service test is displayed for conciseness. The results in terms of speedup and efficiency are seen in Figure \ref{fig:Subg_SE}.
|
||||
A series of tests were conducted on the platform described at the beginning of Section \ref{sec:test-platform}, and results were collected in regards to the effect of the MPI Subgraphing approach on 4 example networks that had a testing arrangement as follows:
|
||||
\begin{itemize}
|
||||
\item{All tests ran for 12 months, with time steps of 1 month.}
|
||||
\item{All tests had the same number of compliance checks: brake pads, exhaust pipes, vacuum pumps, and AC filters.}
|
||||
\item{There were 10 base exploits, and an additional 4 exploits were individually added in the form of services for each test.}
|
||||
\item{All tests used the same network model.}
|
||||
\item{Services must be performed prior to advancing time, if services are applicable.}
|
||||
\item{Graph visualization was not timed. Only the generation and database operation time was measured.}
|
||||
\end{itemize}
|
||||
|
||||
All tests used synchronous firing. Figure \ref{fig:Subg_base} shows the runtimes of each of the test cases. Only the serial runtime from the 2 Service test is displayed for conciseness. The results in terms of speedup and efficiency are seen in Figure \ref{fig:Subg_SE}.
|
||||
|
||||
\begin{figure}[htp]
|
||||
\includegraphics[width=\linewidth]{"./Chapter5_img/MPISubg_RT_No_DHT.png"}
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
This is pdfTeX, Version 3.141592653-2.6-1.40.23 (TeX Live 2021/Arch Linux) (preloaded format=pdflatex 2022.3.21) 4 APR 2022 20:42
|
||||
This is pdfTeX, Version 3.141592653-2.6-1.40.23 (TeX Live 2021/Arch Linux) (preloaded format=pdflatex 2022.3.21) 4 APR 2022 21:04
|
||||
entering extended mode
|
||||
restricted \write18 enabled.
|
||||
%&-line parsing enabled.
|
||||
@ -477,53 +477,53 @@ ine 202.
|
||||
LaTeX Warning: No positions in optional float specifier.
|
||||
Default added (so using `tbp') on input line 216.
|
||||
|
||||
[46 <./Chapter5_img/front_merge.drawio.png>]
|
||||
<./Chapter5_img/MPISubg_RT_No_DHT.png, id=233, 399.018pt x 250.098pt>
|
||||
[46 <./Chapter5_img/front_merge.drawio.png>] [47]
|
||||
<./Chapter5_img/MPISubg_RT_No_DHT.png, id=236, 399.018pt x 250.098pt>
|
||||
File: ./Chapter5_img/MPISubg_RT_No_DHT.png Graphic file (type png)
|
||||
<use ./Chapter5_img/MPISubg_RT_No_DHT.png>
|
||||
Package pdftex.def Info: ./Chapter5_img/MPISubg_RT_No_DHT.png used on input li
|
||||
ne 244.
|
||||
ne 254.
|
||||
(pdftex.def) Requested size: 469.75499pt x 294.44524pt.
|
||||
<./Chapter5_img/no_DHT_Spd.png, id=234, 424.422pt x 249.003pt>
|
||||
<./Chapter5_img/no_DHT_Spd.png, id=237, 424.422pt x 249.003pt>
|
||||
File: ./Chapter5_img/no_DHT_Spd.png Graphic file (type png)
|
||||
<use ./Chapter5_img/no_DHT_Spd.png>
|
||||
Package pdftex.def Info: ./Chapter5_img/no_DHT_Spd.png used on input line 252.
|
||||
Package pdftex.def Info: ./Chapter5_img/no_DHT_Spd.png used on input line 262.
|
||||
|
||||
(pdftex.def) Requested size: 469.75499pt x 275.60631pt.
|
||||
<./Chapter5_img/no_DHT_eff.png, id=235, 429.021pt x 249.222pt>
|
||||
<./Chapter5_img/no_DHT_eff.png, id=238, 429.021pt x 249.222pt>
|
||||
File: ./Chapter5_img/no_DHT_eff.png Graphic file (type png)
|
||||
<use ./Chapter5_img/no_DHT_eff.png>
|
||||
Package pdftex.def Info: ./Chapter5_img/no_DHT_eff.png used on input line 253.
|
||||
Package pdftex.def Info: ./Chapter5_img/no_DHT_eff.png used on input line 263.
|
||||
|
||||
(pdftex.def) Requested size: 469.75499pt x 272.8939pt.
|
||||
[47] [48 <./Chapter5_img/MPISubg_RT_No_DHT.png>] [49 <./Chapter5_img/no_DHT_Sp
|
||||
d.png> <./Chapter5_img/no_DHT_eff.png>]
|
||||
[48 <./Chapter5_img/MPISubg_RT_No_DHT.png>] [49 <./Chapter5_img/no_DHT_Spd.png
|
||||
> <./Chapter5_img/no_DHT_eff.png>]
|
||||
<./Chapter5_img/dup.drawio.png, id=248, 815.045pt x 744.7825pt>
|
||||
File: ./Chapter5_img/dup.drawio.png Graphic file (type png)
|
||||
<use ./Chapter5_img/dup.drawio.png>
|
||||
Package pdftex.def Info: ./Chapter5_img/dup.drawio.png used on input line 261.
|
||||
Package pdftex.def Info: ./Chapter5_img/dup.drawio.png used on input line 271.
|
||||
|
||||
(pdftex.def) Requested size: 469.75499pt x 429.25806pt.
|
||||
<./Chapter5_img/Dup_DHT.png, id=249, 796.065pt x 483.99pt>
|
||||
File: ./Chapter5_img/Dup_DHT.png Graphic file (type png)
|
||||
<use ./Chapter5_img/Dup_DHT.png>
|
||||
Package pdftex.def Info: ./Chapter5_img/Dup_DHT.png used on input line 268.
|
||||
Package pdftex.def Info: ./Chapter5_img/Dup_DHT.png used on input line 278.
|
||||
(pdftex.def) Requested size: 469.75499pt x 285.59593pt.
|
||||
[50] [51 <./Chapter5_img/dup.drawio.png>] [52 <./Chapter5_img/Dup_DHT.png>]
|
||||
<./Chapter5_img/DHT_Spd.png, id=262, 421.575pt x 233.235pt>
|
||||
File: ./Chapter5_img/DHT_Spd.png Graphic file (type png)
|
||||
<use ./Chapter5_img/DHT_Spd.png>
|
||||
Package pdftex.def Info: ./Chapter5_img/DHT_Spd.png used on input line 278.
|
||||
Package pdftex.def Info: ./Chapter5_img/DHT_Spd.png used on input line 288.
|
||||
(pdftex.def) Requested size: 469.75499pt x 259.89395pt.
|
||||
<./Chapter5_img/DHT_Eff.png, id=263, 422.889pt x 233.235pt>
|
||||
File: ./Chapter5_img/DHT_Eff.png Graphic file (type png)
|
||||
<use ./Chapter5_img/DHT_Eff.png>
|
||||
Package pdftex.def Info: ./Chapter5_img/DHT_Eff.png used on input line 279.
|
||||
Package pdftex.def Info: ./Chapter5_img/DHT_Eff.png used on input line 289.
|
||||
(pdftex.def) Requested size: 469.75499pt x 259.08965pt.
|
||||
<./Chapter5_img/DHT_noDHT.png, id=264, 806.577pt x 496.692pt>
|
||||
File: ./Chapter5_img/DHT_noDHT.png Graphic file (type png)
|
||||
<use ./Chapter5_img/DHT_noDHT.png>
|
||||
Package pdftex.def Info: ./Chapter5_img/DHT_noDHT.png used on input line 285.
|
||||
Package pdftex.def Info: ./Chapter5_img/DHT_noDHT.png used on input line 295.
|
||||
(pdftex.def) Requested size: 469.75499pt x 289.27902pt.
|
||||
) [53] [54 <./Chapter5_img/DHT_Spd.png> <./Chapter5_img/DHT_Eff.png>] [55 <./Ch
|
||||
apter5_img/DHT_noDHT.png>]
|
||||
@ -605,7 +605,7 @@ ts/type1/public/amsfonts/cm/cmr12.pfb></usr/share/texmf-dist/fonts/type1/public
|
||||
y10.pfb></usr/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmti12.pfb></usr/
|
||||
share/texmf-dist/fonts/type1/public/amsfonts/cm/cmtt12.pfb></usr/share/texmf-di
|
||||
st/fonts/type1/public/cm-super/sfrm1200.pfb>
|
||||
Output written on Schrick-Noah_MS-Thesis.pdf (74 pages, 2636301 bytes).
|
||||
Output written on Schrick-Noah_MS-Thesis.pdf (74 pages, 2636912 bytes).
|
||||
PDF statistics:
|
||||
344 PDF objects out of 1000 (max. 8388607)
|
||||
192 compressed objects within 2 object streams
|
||||
|
||||
Binary file not shown.
@ -155,7 +155,7 @@
|
||||
\fifthmember{} % as needed
|
||||
\sixthmember{} % as needed
|
||||
|
||||
\numofpages{73} % number of pages in the document
|
||||
\numofpages{74} % number of pages in the document
|
||||
\numofchapters=6 % number of chapters in the document
|
||||
\lastchapter{Conclusions and Future Works} % the title of the last numbered chapter
|
||||
\numofabstractwords{196} % number of words in the abstract
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user