What this benchmark shows is the lightweightness of the memory needed per websocket. 500k users is really impressive. 500k users per machine is great if they a

What this benchmark shows is the lightweightness of the memory needed per websocket. 500k users is really impressive. 500k users per machine is great if they are mostly idle. This is the use case of WhatsApp, and their stats are[1]: > Peaked at 2.8M connections per server > 571k packets/sec > >200k dist msgs/sec Not every app is meant to have mostly idle users. Can a real-time MMO FPS be done in the Haskell server is the question (lets limit each user's neighbourhood to the 10 closest players). I'd be very interested in the other corners of the envelope for the Haskell server: A requests/second benchmark over websockets, with the associated latency HdrHistogram, like [2] [1] http://highscalability.com/blog/2014/2/26/the-whatsapp-architecture-facebook-bought-for-19-billion.html http://highscalability.com/blog/2014/2/26/the-whatsapp-archi... [2] http://www.ostinelli.net/a-comparison-between-misultin-mochiweb-cowboy-nodejs-and-tornadoweb/ http://www.ostinelli.net/a-comparison-between-misultin-mochi...