Commits

Fred T-H  committed 2e1a36e

More significant images.

  • Participants
  • Parent commits 65091f0

Comments (0)

Files changed (1)

File Benchmarks.wiki

 
 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 [[http://github.com/whoppix/erlang-statistics|erlang-statistics]]
+Here are the memory statistics, done with [[http://github.com/whoppix/erlang-statistics|erlang-statistics]] on a 300 seconds run.
 
-{{http://i.imgur.com/5EpQCh.jpg|Memory usage}}
+{{http://i.imgur.com/3ao1Rh.jpg|Memory usage}}
 
-{{http://i.imgur.com/mNGKTh.jpg|Modules loaded}}
+{{http://i.imgur.com/l7lILh.jpg|Modules loaded}}
 
-{{http://i.imgur.com/oZLe4h.jpg|IO}}
+{{http://i.imgur.com/RXo3Ih.jpg|IO}}
 
 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.
 
-{{http://i.imgur.com/UQpKxh.jpg|Resources}}
+{{http://i.imgur.com/Dqz6Nh.jpg|Resources}}
 
-{{http://i.imgur.com/XHhAnh.jpg|Garbage Collection}}
+{{http://i.imgur.com/064KDh.jpg|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.