Added Purpose, descrition of structural and load scalability
This commit is contained in:
parent
edf0ed2334
commit
079d997a8c
4 changed files with 55 additions and 25 deletions
|
@ -86,7 +86,7 @@
|
||||||
\secnumdepth 2
|
\secnumdepth 2
|
||||||
\tocdepth 2
|
\tocdepth 2
|
||||||
\paragraph_separation indent
|
\paragraph_separation indent
|
||||||
\defskip smallskip
|
\defskip medskip
|
||||||
\quotes_language english
|
\quotes_language english
|
||||||
\papercolumns 1
|
\papercolumns 1
|
||||||
\papersides 1
|
\papersides 1
|
||||||
|
@ -323,7 +323,23 @@ Background
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Purpose
|
Purpose
|
||||||
|
\end_layout
|
||||||
|
|
||||||
|
\begin_layout Standard
|
||||||
|
The purpose of the GGS project is to create a scalable and fault tolerant
|
||||||
|
server, while still allowing the server to be as generic as possible.
|
||||||
|
These three italicised terms need some explanation.
|
||||||
|
\end_layout
|
||||||
|
|
||||||
|
\begin_layout Standard
|
||||||
|
Scalability in computer science is a large topic and is commonly divided
|
||||||
|
into sub-fields, two of which are structural scalability and load scalability.
|
||||||
|
These two issues are addressed in this thesis.
|
||||||
|
Structural scalability means expanding an architecture, e.g.
|
||||||
|
adding nodes to a system, without requiring modification of the system.
|
||||||
|
Load scalability means using the available resources in a way which allows
|
||||||
|
handling increasing load, e.g more users, gracefully.
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
|
@ -985,7 +1001,7 @@ Understanding OTP
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Usability
|
Usability
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Chapter
|
\begin_layout Chapter
|
||||||
|
@ -997,7 +1013,7 @@ Software development methodology
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Statistics
|
Statistics
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Chapter
|
\begin_layout Chapter
|
||||||
|
@ -1007,7 +1023,7 @@ Conclusion
|
||||||
\begin_layout Standard
|
\begin_layout Standard
|
||||||
\begin_inset CommandInset bibtex
|
\begin_inset CommandInset bibtex
|
||||||
LatexCommand bibtex
|
LatexCommand bibtex
|
||||||
bibfiles "journals"
|
bibfiles "bibliography"
|
||||||
options "plainnat"
|
options "plainnat"
|
||||||
|
|
||||||
\end_inset
|
\end_inset
|
||||||
|
|
|
@ -65,3 +65,15 @@
|
||||||
publisher = {University of Michigan},
|
publisher = {University of Michigan},
|
||||||
address = {Ann Arbor, MI, USA},
|
address = {Ann Arbor, MI, USA},
|
||||||
}
|
}
|
||||||
|
|
||||||
|
@phdthesis{Armstrong03,
|
||||||
|
author = {Joe Armstrong},
|
||||||
|
institution = {KTH, Microelectronics and Information Technology, IMIT},
|
||||||
|
pages = {xii, 283},
|
||||||
|
publisher = {Mikroelektronik och informationsteknik},
|
||||||
|
school = {KTH, Microelectronics and Information Technology, IMIT},
|
||||||
|
title = {Making reliable distributed systems in the presence of software errors},
|
||||||
|
series = {Trita-IMIT. LECS},
|
||||||
|
number = {03:09},
|
||||||
|
year = {2003}
|
||||||
|
}
|
||||||
|
|
|
@ -86,7 +86,7 @@
|
||||||
\secnumdepth 2
|
\secnumdepth 2
|
||||||
\tocdepth 2
|
\tocdepth 2
|
||||||
\paragraph_separation indent
|
\paragraph_separation indent
|
||||||
\defskip smallskip
|
\defskip medskip
|
||||||
\quotes_language english
|
\quotes_language english
|
||||||
\papercolumns 1
|
\papercolumns 1
|
||||||
\papersides 1
|
\papersides 1
|
||||||
|
@ -323,7 +323,23 @@ Background
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Purpose
|
Purpose
|
||||||
|
\end_layout
|
||||||
|
|
||||||
|
\begin_layout Standard
|
||||||
|
The purpose of the GGS project is to create a scalable and fault tolerant
|
||||||
|
server, while still allowing the server to be as generic as possible.
|
||||||
|
These three italicised terms need some explanation.
|
||||||
|
\end_layout
|
||||||
|
|
||||||
|
\begin_layout Standard
|
||||||
|
Scalability in computer science is a large topic and is commonly divided
|
||||||
|
into sub-fields, two of which are structural scalability and load scalability.
|
||||||
|
These two issues are addressed in this thesis.
|
||||||
|
Structural scalability means expanding an architecture, e.g.
|
||||||
|
adding nodes to a system, without requiring modification of the system.
|
||||||
|
Load scalability means using the available resources in a way which allows
|
||||||
|
handling increasing load, e.g more users, gracefully.
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
|
@ -985,7 +1001,7 @@ Understanding OTP
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Usability
|
Usability
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Chapter
|
\begin_layout Chapter
|
||||||
|
@ -997,7 +1013,7 @@ Software development methodology
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Statistics
|
Statistics
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Chapter
|
\begin_layout Chapter
|
||||||
|
|
|
@ -86,7 +86,7 @@
|
||||||
\secnumdepth 2
|
\secnumdepth 2
|
||||||
\tocdepth 2
|
\tocdepth 2
|
||||||
\paragraph_separation indent
|
\paragraph_separation indent
|
||||||
\defskip smallskip
|
\defskip medskip
|
||||||
\quotes_language english
|
\quotes_language english
|
||||||
\papercolumns 1
|
\papercolumns 1
|
||||||
\papersides 1
|
\papersides 1
|
||||||
|
@ -985,7 +985,7 @@ Understanding OTP
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Usability
|
Usability
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Chapter
|
\begin_layout Chapter
|
||||||
|
@ -994,24 +994,10 @@ Results and discussion
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Software development methodology
|
Software development methodology
|
||||||
\begin_inset CommandInset citation
|
|
||||||
LatexCommand citet
|
|
||||||
key "Knuth:1997:ACP:260999"
|
|
||||||
|
|
||||||
\end_inset
|
|
||||||
|
|
||||||
|
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
Statistics
|
Statistics
|
||||||
\begin_inset CommandInset citation
|
|
||||||
LatexCommand citet
|
|
||||||
key "armstrong2011"
|
|
||||||
|
|
||||||
\end_inset
|
|
||||||
|
|
||||||
|
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Chapter
|
\begin_layout Chapter
|
||||||
|
|
Reference in a new issue