Leaderboard

To convert 200 MB to kilobytes and then bytes you times by 1024, not 1000. Bits scale is normal metric. So 200 * 1024 * 1024 = 209,715,200 times 8 to convert to bits = 1677721600 divided by 1000 3X to arrive back at Gigabits = 1.68 Gbps So if you have 1.68 Gbps, you can transfer 200 MB in 1 second. But yes, there is overhead. To calculate overhead in windows you can do this. make sure network activity is quiet during this test from the command prompt type netstat -e take note of the current the number of "Bytes Received" and "Bytes Sent" type the following using the IP of one of TestMy.net's servers ttcp -t -h0 -D -l1 -n10 -p9 xxx.xx.xx.xx -- this will send 10 bytes to the target. example to get the IP, type ping dallas.testmy.net -- the IP for that server right now is 45.32.203.96 so the command would be ttcp -t -h0 -D -l1 -n10 -p9 45.32.203.96 netstat -e again and subtract "Bytes Received" and "Bytes Sent" from the previous numbers then add them together to get the total bytes transferred, also subtract the 10 bytes you sent... the remaining number is your overhead. https://docs.microsoft.com/en-us/windows/win32/winsock/calculating-overhead-with-netstat-2 Been a while since I've tried this, just tried in Windows 10 and it says ttcp command not found... guess I need to read up on that again. But really, as a consumer... I feel you really don't need to be concerned about network overhead. Here's an article from 2013 on network overhead but it's still relevant today https://packetpushers.net/tcp-over-ip-bandwidth-overhead/ Reality is that overhead really depends on the size of the transfer. It's probably in the neighborhood of 3-7%... more likely on the lower end. Meaning that 1.73 - 1.8 Gbps would be needed instead of 1.68 Gbps in the scenario above. So you might lose 50 to 120 Mbps in overhead on such a fast connection but I feel that's pretty minimal in the grand scheme. If you're pushing nearly 2 Gbps... do you really care about losing 0.05 to 0.12 Gbps of it? ... I think I could manage.