From 87ff58b7d652f9b54d62a639edbeb08f8b122c04 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 22:45:37 +0200 Subject: [PATCH 1/2] Revised 5.1 --- report.lyx | 29 +++++++---------------------- 1 file changed, 7 insertions(+), 22 deletions(-) diff --git a/report.lyx b/report.lyx index 9fd5831..e978034 100644 --- a/report.lyx +++ b/report.lyx @@ -7584,31 +7584,11 @@ In this chapter the results of the GGS prototype are presented and discussed. \begin_layout Section Statistics -\begin_inset Note Note -status open - -\begin_layout Plain Layout -Mention the hardware which the GGS was run on; A Thinkpad T410 with a core - i5 and 4GB of ram. -\end_layout - -\end_inset - - \end_layout \begin_layout Standard -\begin_inset Note Note -status open - -\begin_layout Plain Layout -The testing of the GGS prototype occurred in two sessions -\end_layout - -\end_inset - Testing of the GGS took place in two separate sessions. - The first session simulates a highly demanding application, the second + The first session simulated a highly demanding application, the second session simulated a less demanding application. The highly demanding application is a real time game which does several asynchronous database writes each second. @@ -7723,6 +7703,11 @@ In the second testing session the delay between the server and clients was messages are put in a queue within the system. \end_layout +\begin_layout Standard +It should be noted that with distribution in place, having the GGS deployed + on several machines, test results could reveal much higher numbers. +\end_layout + \begin_layout Standard \begin_inset Note Note status collapsed @@ -7997,7 +7982,7 @@ The GGS was originally intended to be a distributed application, running \begin_layout Standard Distribution was however not implemented in the GGS. Other parts of the GGS were prioritized. - A futute improvement is therefore to implement distribution in the GGS. + A future improvement is therefore to implement distribution in the GGS. A simple way to achieve this is to keep one GGS instance as a coordinating instance, and to keep clients on other instances of the GGS, which can be dynamically added as new clients connect. From 6bced613d0e5ae3f4ca3587ac7f9b889d9d28fdb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 22:47:44 +0200 Subject: [PATCH 2/2] Revised entire chapter 5 --- report.lyx | 24 +++++------------------- 1 file changed, 5 insertions(+), 19 deletions(-) diff --git a/report.lyx b/report.lyx index 5bc173b..0ce811c 100644 --- a/report.lyx +++ b/report.lyx @@ -6060,8 +6060,9 @@ In Erlang, there is a simple version of supervisors. No state of the processes being supervised is inspected. There is, however a specification of how the supervised processes should behave, but on a higher level. - The specification describes things such as how many times in a given interval a child process may crash, which processes need restarting when - crashes occur, etc. + The specification describes things such as how many times in a given interval + a child process may crash, which processes need restarting when crashes + occur, etc. \end_layout @@ -6119,8 +6120,8 @@ reference "fig:The-supervisor-structure" \begin_layout Standard A choice has been made to let faulty processes crash very easily when they receive bad data, or something unexpected happens. - The alternative to crashing would have been to try to fix this faulty - data, or to foresee the unexpected events. + The alternative to crashing would have been to try to fix this faulty data, + or to foresee the unexpected events. This was not chosen since it is so simple to monitor and restart processes, and so difficult to try to mend broken states. This approach is something widely deployed in the Erlang world, and developers @@ -8082,21 +8083,6 @@ textbf{ETS}}{Erlang Term Storage} \end_layout -\begin_layout Subsection -Documentation -\end_layout - -\begin_layout Standard -To start the GGS is not self explanatory. - This together with overall usage of GGS should be documented. - The interface for usage of game developers are also in need of documentation. - Features and requirements with respect to the GGS would assist users to - know what they need to use the GGS and how they would benefit of it. - The GGS does not support many programming languages nor does it have a - complete documentation. - This needs to be taken care of in future versions. -\end_layout - \begin_layout Chapter Conclusion \end_layout