2 ms·
I'm not sure what to tell you. It's literally based on a sound mathematics formula and the RFC that dictates how TCP operates. The only way you're getting max
by tw04 10y ago
I'm not sure what to tell you. It's literally based on a sound mathematics formula and the RFC that dictates how TCP operates. The only way you're getting maxed out gigabit with 11ms latency on a single stream is if you've got something on the pipe telling the TCP/IP stack to violate the RFC - IE: a piece of hardware like cisco waas, silverpeak, riverbed, etc.
There are literally hundreds of TCP throughput calculators out there and they all use the same formula.
- rayiner 10y agoTCP throughout is limited by window size divided by round trip time (I.e. How much you can send before having to wait for an ACK). With RFC 1323, you can specify a window size well above the 65,536 limit that would otherwise exist. With scaling you can have a window size up to a gigabyte. With an RTT of 11 ms, you can saturate a 150 Mbps link with a window size of 160-170kb.
- kalleboo 10y agoI have a cheap shared server on the other side of the planet (250ms latency). Your calculator says I can get at most 2 Mbps(!), which is complete crap. With a single stream (rsync) I typically get around 80 Mbps.