One of the questions I get asked several times a week by my clients is as such. While most people never associate latency with the amount of data they can send across a single TCP stream, engineers need to understand this concept.
Luckily, someone has done most of the leg work for us. Many years ago, a college forwarded me a thesis paper written by Jesper Dangaard Brouer from Copenhagen University in Denmark. While this paper mainly focuses on issues concerning ADSL, he does analyze our exact question on page 21. (28 on the pdf)
Throughput = Window Size / RTT
This very simple formula is the key to your single stream transmission rates. Your throughput on a single stream TCP connection is limited to the WindowSize divided by your RTT or latency. So lets try this out…
roto:/usr/local/sand# ping 18.104.22.168
PING 22.214.171.124 (126.96.36.199) 56(84) bytes of data.
64 bytes from 188.8.131.52: icmp_seq=1 ttl=51 time=69.0 ms
64 bytes from 184.108.40.206: icmp_seq=2 ttl=51 time=69.6 ms
64 bytes from 220.127.116.11: icmp_seq=3 ttl=51 time=67.1 ms
64 bytes from 18.104.22.168: icmp_seq=4 ttl=51 time=69.1 ms
64 bytes from 22.214.171.124: icmp_seq=5 ttl=51 time=69.2 ms
--- 126.96.36.199 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 67.113/68.848/69.687/0.954 ms
That shows our connections average RTT is 69ms. And you should by now know that your TCP Window size for Ethernet is 65,535 bytes. When we plug this data into our formula, it shows..
65535 / 69 = 949.78 kBytes/s
Or about 7.4mbit per second. Lets go ahead and see what kind of data we can come up with by running our own test.
roto:/usr/local/sand# tcpspray -n 2000 188.8.131.52
Transmitted 8048000 bytes in 8.400634 seconds (902.094 kbytes/s. 7216.748 kbits/s)
Thats pretty close, 7.2 mbit per second. Now, these results wont always come out as perfect, but it will give you a good idea of what to expect. Just remember, QOS will affect your results, so please disable it while testing. If you have any questions, please feel free to leave a comment. Thanks you!
note: ip address changed to protect public networks
Network engineer turned management currently servicing the enterprise data center market. I started working on networks in the ’90s and still feel like that was just a few years ago. Jack of all trades, master of none; I love to learn about everything. Feel free to ask me about photography, woodworking, nhra, watches, or even networking! — For feedback, please leave a comment on the article in question, and I’ll respond as soon as I can. For everything else including fan mail or death threats, contact me via twitter.