Fred T-H committed 0efbcc1

2 hours run mem pics

Comments (0)

Files changed (1)

 The send/received ratios remain similar, and the average per client too.  The core of the chat server can thus theoretically handle over 15000 users sending each other messages every 5 second without too much degradation in response time per user. Note that at that point, the shut down of processes became a bit hard on my laptop and user timeouts started appearing (after the results were done and clients disconnected). 
-Here are the memory statistics, done with [[|erlang-statistics]] on a 300 seconds run.
+Here are the memory statistics, done with [[|erlang-statistics]] on a 2 hours run with 15 000 users.
-{{|Memory usage}}
+{{|Memory usage}}
 Half the memory seems to be taken by the processes themselves, and the other half by what they contain. It is likely the message history in each user (10 messages each, max) is what's driving it up. The drop near 11:10 is likely the 10th message being swapped out across many users.
-{{|Modules loaded}}
+{{|Modules loaded}}
 On this one, the huge IO peak is the benchmark code announcing the creation of each user process. It falls down afterwards, once the real messaging begins.
-{{|Garbage Collection}}
+{{|Garbage Collection}}
 Real world trials would be needed to further show reliability of Chut's core, but so far I'm pretty satisfied with the results.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.