aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-February/000229.html
blob: eafe24591ec662465d469915ca413bd2796ba3e0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Nel] Dynamic load balancing?</TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:thierry%40mallard.com">
   <LINK REL="Previous"  HREF="000217.html">
   <LINK REL="Next" HREF="000230.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Nel] Dynamic load balancing?</H1>
    <B>Thierry Mallard</B> 
    <A HREF="mailto:thierry%40mallard.com"
       TITLE="[Nel] Dynamic load balancing?">thierry@mallard.com</A><BR>
    <I>Tue, 20 Feb 2001 10:56:54 +0100</I>
    <P><UL>
        <LI> Previous message: <A HREF="000217.html">[Nel] Dynamic load balancing?</A></li>
        <LI> Next message: <A HREF="000230.html">[Nel] Dynamic load balancing?</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#229">[ date ]</a>
              <a href="thread.html#229">[ thread ]</a>
              <a href="subject.html#229">[ subject ]</a>
              <a href="author.html#229">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Mon, Feb 19, 2001 at 03:43:59PM -0600, Jared Mark wrote:
&gt;<i> Okay, so what you're saying is basically this...
</I>&gt;<i> 
</I>&gt;<i> By seperating the services, you can have a cluster of machines, each running
</I>&gt;<i> different services, and thus, keeping the load down across the board.  You
</I>&gt;<i> would have a single system, for example, handling just combat resolution,
</I>&gt;<i> and you would have another system that would keep track of the database...
</I>
We may have to add features concerning high-availability, as this scheme
doesn't allow it : if the computing holding the combat resolution fails, the
world will be a heaven of peace  ;-)

The second point is that if a service grow too much, the load-balancing won't
respond to the problem. You mentionned this point in your previous mail I
think.

One possible architecture is to write separate process, and give two or three
computer the responsiblity to distribute, by monitoring the farm, those
process. I dunno if such scheme is possible w.r.t. the current NeL objectives
(?)

Best regards,

	Shaman

-- 
Thierry Mallard              |              
GnuPG key on wwwkeys.pgp.net |
key 0xA3D021CB               |
<A HREF="http://thierry.mallard.com">http://thierry.mallard.com</A>   |     


</pre>




<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI> Previous message: <A HREF="000217.html">[Nel] Dynamic load balancing?</A></li>
	<LI> Next message: <A HREF="000230.html">[Nel] Dynamic load balancing?</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#229">[ date ]</a>
              <a href="thread.html#229">[ thread ]</a>
              <a href="subject.html#229">[ subject ]</a>
              <a href="author.html#229">[ author ]</a>
         </LI>
       </UL>
</body></html>