Websocket Server Handling Millions of Concurrent Users: True or False?

Some providers of enterprise WebSocket servers claim their real-time web technology scales to millions of users. However, AFAIK, only MigratoryData currently offers evidence of how this scaling is achieved. Some claims:

Kaazing

A true veteran performance guru (Kirk Pepperdine) joins the Kaazing team to verify test Kaazing’s 1 million connection benchmark on a 1U blade

Lightstreamer

… platform for pushing live data over WebSockets and other web protocols, scalable up to millions of users

Pusher

Scaling infrastructure to maintain millions of long running connections is not trivial, but we’ve worked out the tricks to handle it with ease

MigratoryData

A single MigratoryData instance is able to handle up to 1 million concurrent users (see benchmarks)”

Most likely, all the products mentioned above come with some form of clustering. Thus, this feature can be used to scale horizontally and push data to millions of concurrent users by deploying multiple WebSocket server instances. In this case, scaling to millions of users is possible but expensive.

MigratoryData implements built-in high availability clustering, thus it scales horizontally. But more important, MigratoryData demonstrates (as published in their Performance Benchmarking Guide) that pushing real-time data while having 1 million concurrent users connected is possible from a single instance running on a 1U blade. Thus, MigratoryData is able to push data to millions of users and, in fact, it is currently used in production to push real-time data to millions of end-users every day.

Over the next couple of weeks, I’m going to work on the performance benchmarking of the just released MigratoryData WebSocket Server 4.0 (see the Architecture Guide for an overview of the new version 4.0).

Last time when I performed benchmark tests for MigratoryData server 3.5, I compared the results with those published by Caplin Systems for their WebSocket server Caplin Liberator. Caplin Liberator’s performance results were very good in terms of latency and throughput and I think (if I recall correctly) we’ve achieved comparable results, slightly better for some use-cases and slightly worse for other ones. Caplin Systems’ target at that time was not high vertical scalability, as suggested by Martin Tyler.

I’m interested if any WebSocket server provider that claims high vertical scalability can offer any published results so that I can compare them with the new results of MigratoryData 4.0. MigratoryData benchmark results for version 4.0 are going to be released soon.

 

4 thoughts on “Websocket Server Handling Millions of Concurrent Users: True or False?

  1. Mihai Rotaru Post author

    I saw today another unclear message from Kaazing where it is publicly announced that they broke the “one million connections” barrier.

    In reality, the one million users do not connect to a single WebSocket server instance but to 43 WebSocket server instances running on a “single rack” consisting of 43 powerful Dell R620 servers.

    Thus, the real vertical scalability demonstrated by Kaazing in the benchmark announced today is 24,000 concurrent connections.

    Reply
  2. Martin Tyler

    Hi Mahai,

    Interested to see your new benchmarks. We haven’t got any new benchmarks to publish for Caplin Liberator unfortunately.

    I saw the Kaazing announcement too – all very vague! with different articles saying different things:

    ‘on a single Dell PowerEdge R620 server’
    ‘on Dell PowerEdge R620 12th generation servers’
    ‘on a single Dell PowerEdge R620 rack’

    Quite an important detail!

    Reply
    1. Mihai Rotaru Post author

      Hi Martin,

      I will publish the benchmark results of MigratoryData 4.0 on this blog as soon as we will do new tests.

      As usual, any comment from you will be much appreciated.

      Cheers,
      Mihai

      Reply
  3. Martin Tyler

    I’ll be publishing the ‘Caplin Liberator delivers 100 msgs/sec to 100 billion users’ blog soon too, just as soon as Dell loan us enough servers to do that 🙂

    Looking forward to your results, and I hope to have some time soon to run some new genuine tests on Liberator.

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s