Skip to content
Omnikalc

TCP throughput calculator: how fast a single connection can go with latency and packet loss

Enter the RTT, the packet loss, the MSS, the receive window and the link capacity to get the expected throughput of a TCP connection with the Mathis formula, and the window needed to fill the link.

Updated on
Your inputs
bytes

Value out of range

ms

Value out of range

%

Value out of range

KB

Value out of range

Mbps

Value out of range

Results

Expected TCP throughput

9.05 Mbps

Limit from packet loss (Mathis)
9.05 Mbps
Limit from the receive window
41.94 Mbps
Share of the link used
0.9 %
Only a small part of the link is used: loss or the window is the bottleneck
Window needed to fill the link
6,104 KB

Why does a download not use the full line? A single TCP connection is limited by the round-trip time, by the packet loss and by the window of the receiver. The TCP throughput calculator applies the Mathis formula and the window limit, and gives the expected throughput, the share of the link used and the window needed to fill the link.

How the calculation works

  • Enter the MSS (1460 bytes on Ethernet), the round-trip time of the path and the packet loss rate.
  • Enter the receive window of the receiver and the capacity of the slowest link on the path.
  • The calculator applies the Mathis formula, throughput ≈ (MSS / RTT) × 1.22 / √p, where p is the loss rate, and the window limit of window / RTT.
  • The throughput is the smallest of the three limits. The result also gives the share of the link used and the window needed to fill the link.

Example

A path has an MSS of 1460 bytes, an RTT of 50 ms, a loss rate of 0.1 %, a receive window of 256 KB and a 1000 Mbps link. The loss limit is 1460 × 8 / 0.05 × 1.2247 / √0.001 = 9.05 Mbps, the window limit is 41.94 Mbps, and the throughput is 9.05 Mbps: only 0.9 % of the link. To fill the link you would need a window of 6,104 KB, and almost no loss.

Why it matters

The calculator helps network engineers, gamers, remote workers and people who move large files over a long distance to understand why a connection is slow and what to change. It is also used to explain the effect of loss on a satellite or a wireless link.

Good to know

The Mathis formula is a model of long flows with random loss and a standard congestion control. Real throughput changes with the congestion control, with bursts of loss, with the buffers and with the other flows on the path. Short connections never reach the limit, because the slow start phase takes several round trips. Use the result as an order of magnitude, and measure with a tool such as iperf for a real path.

The bandwidth-delay product calculator gives the data in flight on a path, the network latency calculator estimates the delay of a link, the download time calculator turns a speed into a duration, and the streaming data calculator estimates the data of a video stream.

Frequently asked questions

What is the Mathis formula?

Mathis and his colleagues showed in 1997 that the long-term throughput of a TCP connection with random loss is about (MSS / RTT) × C / √p, with C close to 1.22 for the standard congestion control. It says that throughput falls when the round-trip time grows and when the loss rate grows, but only like the square root of the loss. A loss of 1 % cuts the throughput to a tenth of what a loss of 0.01 % gives.

Why is my speed low on a fast link?

A single TCP connection is limited by the delay and by the loss, not only by the link. On a path with 50 ms of RTT and 0.1 % of loss, the limit is near 9 Mbps, whatever the capacity. Several parallel connections add up, because each one has its own limit, and this is why download tools open many connections. Newer algorithms such as BBR and CUBIC are less sensitive to loss.

What is the receive window limit?

A sender can have at most one window of data not yet acknowledged, so the throughput is at most window / RTT. A window of 64 KB with an RTT of 100 ms gives only 5.2 Mbps. The window scaling option of TCP allows windows up to 1 GB, and modern systems adjust the window by themselves. The last output gives the window that is needed to fill the link, which is the bandwidth-delay product.

How do I improve the throughput?

Reduce the RTT (closer servers, a CDN), lower the loss (better Wi-Fi or cabling, no congested link), use a modern congestion control such as BBR, enable window scaling and use several connections. For a path with long distance and a high capacity, loss matters the most, because the limit goes with 1/√p. The calculator helps to see which factor matters for you.

Was this calculator helpful?

Thanks for your feedback!

Results are estimates provided for information purposes. They do not replace professional advice.