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-March/000317.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-March/000317.html')
| -rw-r--r-- | pipermail/nel/2001-March/000317.html | 101 |
1 files changed, 101 insertions, 0 deletions
diff --git a/pipermail/nel/2001-March/000317.html b/pipermail/nel/2001-March/000317.html new file mode 100644 index 00000000..c94a06de --- /dev/null +++ b/pipermail/nel/2001-March/000317.html @@ -0,0 +1,101 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] Network Connections</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:archer%40nevrax.com"> + <LINK REL="Previous" HREF="000315.html"> + <LINK REL="Next" HREF="000324.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] Network Connections</H1> + <B>Vincent Archer</B> + <A HREF="mailto:archer%40nevrax.com" + TITLE="[Nel] Network Connections">archer@nevrax.com</A><BR> + <I>Thu, 1 Mar 2001 11:46:35 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000315.html">[Nel] Network Connections</A></li> + <LI> Next message: <A HREF="000324.html">[Nel] Network Connections</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#317">[ date ]</a> + <a href="thread.html#317">[ thread ]</a> + <a href="subject.html#317">[ subject ]</a> + <a href="author.html#317">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>According to Tom wright: +><i> 1) i think you are going to find it very difficult to scale a server +</I>><i> to 5000 concurrent users, using any kind of scheme unless its a BIG +</I>><i> server. Look at EQ currently, they struggle with 2000. But this is +</I>><i> just my opinion :-) so feel free to ignore it. +</I> +EQ doesn't struggle with 2000 because of server size. A "server" on EQ +consists (to the best of my knowledge) of about 15 or so quadriprocessor +RISC boards, with all nearly 100 zones (now) spread of these. They +struggle not because the server can't handle the load, but because the +content of the game can't handle the load (i.e. problems stem not from +too many people for CPU time, they stem from too many people for not +enough spawns). + +No MMOG so far can use a single server, no matter how big it is. What +we term server, or shard, or whatever, typical technical litterature +terms 'cluster'. And using the right architecture can make a cluster +very large, until it collapses not from load, but when adding a new +note consumes more CPU spent in inter-node communications than the node +itself adds to the whole. + +><i> 2) On windows NT/2k, using async sockets with events is... +</I>... +><i> 3) Windows did support something called micro threads, which had... +</I> +All these optimisation techniques are nice. But they're heavily dependent +on Windows itself. We do want our server to run under windows, for debugging +purpose (and for the odd amateur out there who would want to run a +smallish server on his home machine), but we clearly do NOT intend our +production servers to run under windows. + +Which is why we're looking at a reasonably portable architecture, and why +these suggestions, as nice as they are, cannot be used, because they tie +too much the architecture :( + +><i> PS A binary of the next release for windows would be nice, takes HOURS to build :-) +</I> +As much as people would love one, it's right now a "marketing" decision, +so that we attract people that really want to look at the source, and not +just people who want to look at the finished product without caring about +how it's done :) + +(However, some Nevrax people, and maybe external people as well, have set + up binary archives on their own private home pages. Ask, and you'll + probably find it. But officially, we do not support or provide these + releases. Yet) + +-- +Vincent Archer Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A> + +Nevrax France. Off on the yellow brick road we go! + +</pre> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000315.html">[Nel] Network Connections</A></li> + <LI> Next message: <A HREF="000324.html">[Nel] Network Connections</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#317">[ date ]</a> + <a href="thread.html#317">[ thread ]</a> + <a href="subject.html#317">[ subject ]</a> + <a href="author.html#317">[ author ]</a> + </LI> + </UL> +</body></html> |