Realtime to the Million!

Statistics

This benchmark was performed with a single WebSocket Server and 16 machines connecting to this server.

Simultaneous Users

Number of simultaneous users connected over time.

Metric Description
Users Number of simultaneous users.
Connected Number of users with an opened connection.

Response Times

Response time at a given point of time.

As seen, the response time was very constant until the limit of one million connections was reached.

Metric Description
Connect Duration in milliseconds of the handshake.
Request Response time in milliseconds for establishing the connection.

Traffic

Network traffic or data traffic moving across the network at a given point of time.

Metric Description
Sent Size of requests in bytes.
Received Size of responses in bytes.

Errors

Errors that occured when trying to connect or during an already established connection.

As seen, there were no errors until the limit of one million connections was reached.

Metric Description
Connect Number of connections that failing to connect.
Disconnect Number of connections that disconnected.

1,000,382

Connected Users

440.06 MB

Total Network Traffic

2.58 ms

Average Response Time

Performance

This benchmark was performed on a DigitalOcean General Purpose Droplet with 32 cores and 128 GB of memory.

Usage

The respective value of what percentage is actually being utilized. The CPU usage is an indicator of how much stress the processor is currently undergoing, and, what capacity is still available.

The drop at 500 seconds results from no more new connections are established. That means, the last value reflects the load to maintain all connections.

Metric Description
Usage CPU Usage in %.

Load

The load represents the average system load over a period of time. 1.0 on a single core cpu represents 100% utilization.
Note that this benchmark is using a machine with 32 cores.

Metric Description
Load CPU Load by cores.

Memory

Amount of system memory used over time in MB.

Metric Description
Used Used memory in MB.

FAQ

What software was used?

We used Tsung to do the benchmark.

Can I see more?

The generated report including all logs can be found on GitHub.