From 43fb94a31d1ff7ef5979348d9fa6087cf4288b12 Mon Sep 17 00:00:00 2001 From: Jeena Paradies Date: Thu, 12 May 2011 17:41:56 +0200 Subject: [PATCH] language in load balancing --- report.lyx | 40 ++++++++++++++++++---------------------- 1 file changed, 18 insertions(+), 22 deletions(-) diff --git a/report.lyx b/report.lyx index 06b074f..6d9b310 100644 --- a/report.lyx +++ b/report.lyx @@ -2573,11 +2573,11 @@ Load balancing \begin_layout Standard The need for load balancing varies among different kind of systems. Small systems that only use one or a couple of servers can cope with a - simple implementation of load balancing, while in large systems it is useful - to have extensive and well working load balancing. - The need also depends on what kind of server structure the system works - on, a static structure where the number of servers are predefined or a - dynamic structure where the number varies. + simple implementation of a load balancer, while in large systems it is + useful to have extensive and well working load balancing implementations. + The need also depends on what kind of server structure the system is working + on, a static structure where the number of servers is predefined or a dynamic + structure where this number varies. \begin_inset ERT status open @@ -2597,11 +2597,12 @@ textbf{Amazon EC2}}{A cloud computation service} \begin_layout Standard Load balancing and scaling are difficult in different scenarios. - When running in a separate server park, there are a set number of servers + When running in a separate server park, there is a set number of servers available, this means that an even distribution on all servers is preferable. When running the GGS in a cloud, such as Amazon EC2, it is possible to - add an almost infinite number of servers as execution goes on. - In this cloud setting, it may be more important to evenly distribute load + add an almost infinite number of servers as execution goes on and the load + increases. + In this cloud setting it may be more important to evenly distribute load on newly added servers. \end_layout @@ -2615,16 +2616,11 @@ Fill up the capacity of one server completely, and then move over to the \end_layout \begin_layout Itemize -Evenly distribute all clients to all servers from the beginning, when load - becomes too high on all of them, then comes a new problem: +Evenly distribute all clients to all servers from the beginning. + When the load becomes too high on all of them a new problem arises: how + do we distribute load on these new servers? \end_layout -\begin_deeper -\begin_layout Itemize -How do we distribute load on these new servers? -\end_layout - -\end_deeper \begin_layout Standard Load balancing is a key component to achieve scalability in network systems. The GGS is a good example of a system that needs to be scalable, to attain @@ -2633,18 +2629,18 @@ Load balancing is a key component to achieve scalability in network systems. provide a stable and fast load balancer. There are certain persistence problems that can occur with load balancing, if a player moves from a server to another data loss may occur. - This is an important aspect to consider when the load balancer is designed + This is an important aspect to consider when a load balancer is designed and implemented. \end_layout \begin_layout Standard Load balancing can often be implemented using dedicated software, this means that in many applications load balancing may not be implemented because - it already exist functional solutions. - This depends on what specific needs the system have and a minor goal of - the project is to analyze whether the GGS project can use existing load - balancing tools or if it is necessary to implement load balancing in the - project. + there already exist functional or even better external solutions. + This depends on what specific needs the system has. + A minor goal of this thesis is to analyze whether the GGS can use existing + load balancing tools or if it is necessary how to implement load balancing + in the project. \end_layout \begin_layout Standard