Fred T-H avatar Fred T-H committed 67a526c

adding details about off delays

Comments (0)

Files changed (1)

 ...
 }}}
 
-Where the ratios are of 0.947, 0.946 and 0.965, respectively. The difference in what's sent and received doesn't seem to depend on time, groups or clients. Thus the cutoff point must be the next rational error cause. Now let's carry on with the benchmarks...
+Where the ratios are of 0.947, 0.946 and 0.965, respectively. The difference in what's sent and received doesn't seem to depend on time, groups or clients. The real question is thus to find whether the discrepancies are due to the delays in messaging every actor to stop its work  (if it takes 4-5 seconds to propagate all messages and act on them) or if there is really a high latency getting there. Testing with a real user should be needed for that. Now let's carry on with the benchmarks...
 
 {{{
 #!text
 Average received per client: 12.252933333333333
 }}}
 
-The send/received ratios remain similar, and the average per client too.  The core of the chat server can thus theoretically handle over 15 000 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). Real world trials would be needed to further show reliability of Chut's core, but so far I'm pretty satisfied with the results.
+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). Real world trials would be needed to further show reliability of Chut's core, but so far I'm pretty satisfied with the results.
+
 
 === Server benchmark ===
 Not done yet.
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 ProjectModifiedEvent.java.
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.