4 ms·
Sever network speedtest against speedtest.net are, mostly and unfortunately, useless for anything connected at >1Gbps. Here are 5 tests run against (presumably)
by aroch 11y ago
Sever network speedtest against speedtest.net are, mostly and unfortunately, useless for anything connected at >1Gbps. Here are 5 tests run against (presumably) the same test server from a server connected at 10Gbps writing to an SSD
>Ping (Lowest): 7.41 ms | Download (Max): 269.98 Mbps | Upload (Max): 1260.40 Mbps
>Ping (Lowest): 7.31 ms | Download (Max): 165.27 Mbps | Upload (Max): 183.88 Mbps
>Ping (Lowest): 7.73 ms | Download (Max): 337.67 Mbps | Upload (Max): 222.73 Mbps
>Ping (Lowest): 7.79 ms | Download (Max): 614.26 Mbps | Upload (Max): 594.96 Mbps
>Ping (Lowest): 7.33 ms | Download (Max): 1468.05 Mbps | Upload (Max): 97.49 Mbps
- cliffwarden 11y agoHow does the speedtest website respond to this same test? If you think this is a bug in the code itself (and not just speedtest in general) i'm happy to dig into this. Just open an issue on github. Thanks!
- aroch 11y agoIts a problem with speedtest, not necessarily your gocode. Other CLI speedtest apps suffer from the same problem.