This test provides a general indication of the number of sessions the network can support. Throughput is a measure of how much data a network can process in a given amount of time. It's also a measure of how quickly a network or device can send and receive data.
This test connects a data channel via the TURN servers of the tested infrastructure, sending data payloads of 1,024 bytes each over the channel for a few seconds and measuring the rate at which they are received. This is done using SCTP protocol relayed via TURN.
This gives a general available throughput indication for the network you are using from the specific machine running the test. It should be taken into account here that SCTP has its own throttling mechanism which is slightly different than the one used by audio and video transmission over WebRTC.
Data we collect and share
| Maximum | The maximum throughput measured throughout the test conducted. |
| Average | The average throughput achieved during the test conducted. |
| Minimum | The minimum throughput measured throughout the test conducted. |
The number of sessions is calculated based on the codecs used in a session and the average bitrate necessary for good transmission of these codecs in a WebRTC session. For G.711, this is calculated as 100kbps per session and for Opus voice calls, this is calculated as 50kbps per session.
Thresholds
| Metric | Good | Mediocre | Bad |
|---|---|---|---|
| Minimum bitrate | Above 4 sessions | 1-4 sessions | Below 1 session |
| Average bitrate | Above 4 sessions | 1-4 sessions | Below 1 session |
| Maximum bitrate | Above 4 sessions | 1-4 sessions | Below 1 session |
| Difference | Below 20% | 20-50% | Over 50% |
Difference means the difference between Average & Minimum or Maximum & Average.
Things to notice
Low minimum throughput as well as high variance between minimum, average and maximum may indicate a connection that is unstable and jittery. If you see this, expect to see the same in jitter data collected in other tests conducted.