diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-February/000229.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-February/000229.html')
| -rw-r--r-- | pipermail/nel/2001-February/000229.html | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/pipermail/nel/2001-February/000229.html b/pipermail/nel/2001-February/000229.html new file mode 100644 index 00000000..eafe2459 --- /dev/null +++ b/pipermail/nel/2001-February/000229.html @@ -0,0 +1,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: +><i> Okay, so what you're saying is basically this... +</I>><i> +</I>><i> By seperating the services, you can have a cluster of machines, each running +</I>><i> different services, and thus, keeping the load down across the board. You +</I>><i> would have a single system, for example, handling just combat resolution, +</I>><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> |