ed/TimothyLottes.github.io
1
0
Fork 0
mirror of https://github.com/gomson/TimothyLottes.github.io.git synced 2026-08-04 14:48:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add files via upload

Browse Source
This commit is contained in:
TimothyLottes
2016-11-09 00:09:00 -05:00
committed by GitHub
parent 790e0206a1
commit 4c909095a1
3 changed files with 54 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
20070706.html
+2 -2
View File
@@ -7,8 +7,8 @@ Here is the paper napkin model which started the idea behind the network logic f
a massively multi-player online game with first person shooter interactivity.
<br>
<br>
<ol><li><a href="070703.htm">Mixed P2P and server centric model</a>.</li>
<li><a href="070705.htm">Maximum of 256 minimum sized UDP packets/sec</a>.</li>
<ol><li><a href="20070703.html">Mixed P2P and server centric model</a>.</li>
<li><a href="20070705.html">Maximum of 256 minimum sized UDP packets/sec</a>.</li>
<li>Goal to get as many players interacting at one time as possible.</li></ol>
<br>
Key concepts.
20070707.html
+47
View File
@@ -0,0 +1,47 @@
<html><head><link rel="stylesheet" href="style.css"></head><body><div class="page">
<h1>20070707 - Management Server</h1>
<br>
In the Atom model, <a href="20070706.html">peer to peer</a> handles most of the player interactions,
and the central server serves as management providing the following key roles.
<br>
<br>
<ol><li>Help connect players, punching holes through firewalls.</li>
<li>Keep the master copy of the persistent world state.</li>
<li>Deal with possible cheating or hacking into the game.</li>
<li>Manage players, stats, rankings, etc.</li></ol>
<br>I use the following tables often when doing server protocol design reality checks. Keeping with a single server,
a <a href="20070703.html">640 GB/month bandwidth</a> quota, and using a 1/9 worst case <a href="20070702.html">percentage of player time online</a>.
<br>
<br>
<ol><li>1000 players = 256 bytes/sec = 15360 bytes/min</li>
<li>5000 players = 51 bytes/sec = 3072 bytes/min</li>
<li>10000 players = 25 bytes/sec = 1536 bytes/min</li>
<li>50000 players = 5 bytes/sec = 307 bytes/min</li>
<li>100000 players = 2 bytes/sec = 153 bytes/min</li></ol>
<br>
And for a 3840 GB/month bandwidth quota.<br>
<br>
<ol><li>1000 players = 1536 bytes/sec = 92160 bytes/min</li>
<li>5000 players = 307 bytes/sec = 18432 bytes/min</li>
<li>10000 players = 153 bytes/sec = 9216 bytes/min</li>
<li>50000 players = 30 bytes/sec = 1843 bytes/min</li>
<li>100000 players = 15 bytes/sec = 921 bytes/min</li>
<li>500000 players = 3 bytes/sec = 184 bytes/min</li>
<li>1000000 players = 1 bytes/sec = 92 bytes/min</li></ol>
<br>
For performance reasons it is a good idea to keep all players data in the active memory of the server,
without overflowing into virtual memory and then slow disc access.
Assuming 256 bytes of data per player.<br>
<br>
<ol><li>65,536 players = 16MB</li>
<li>131,072 players = 32MB</li>
<li>262,144 players = 64MB</li>
<li>524,288 players = 128MB</li>
<li>1,048,576 players = 256MB</li></ol>
</div></body></html>
index.html
+5
View File
@@ -91,6 +91,11 @@ Below this is active random migration (456 prior posts still to filter through)
<a href="20090422.html">20090422 - WFA Image Compression</a><br>
<br>
<b>2007</b><br>
<a href="20070707.html">20070707 - Management Server</a><br>
<a href="20070706.html">20070706 - 510 Players on Screen at 128 Kbps</a><br>
<a href="20070705.html">20070705 - UDP Player Bandwidth</a><br>
<a href="20070704.html">20070704 - Network Latency</a><br>
<a href="20070703.html">20070703 - Cost of Bandwidth</a><br>
<a href="20070702.html">20070702 - Market Research</a><br>
<br>
<b>2004</b><br>