4 ms·
speedtest-cli is garbage if you have >100Mbps Speeds. The dev refuses to acknowledge this: https://github.com/sivel/speedtest-cli/issues/226 https://github.com/
by virtuallynathan 7y ago
speedtest-cli is garbage if you have >100Mbps Speeds. The dev refuses to acknowledge this: https://github.com/sivel/speedtest-cli/issues/226 https://github.com/sivel/speedtest-cli/issues/226
Also not just me:
https://github.com/sivel/speedtest-cli/issues/649 https://github.com/sivel/speedtest-cli/issues/649
https://github.com/sivel/speedtest-cli/issues/648 https://github.com/sivel/speedtest-cli/issues/648
https://github.com/sivel/speedtest-cli/issues/641 https://github.com/sivel/speedtest-cli/issues/641
https://github.com/sivel/speedtest-cli/issues/616 https://github.com/sivel/speedtest-cli/issues/616
https://github.com/sivel/speedtest-cli/issues/601 https://github.com/sivel/speedtest-cli/issues/601
https://github.com/sivel/speedtest-cli/issues/588 https://github.com/sivel/speedtest-cli/issues/588
https://github.com/sivel/speedtest-cli/issues/546 https://github.com/sivel/speedtest-cli/issues/546
- Nextgrid 7y agoCounterpoint: it’s accurate for me on a 1Gbps symmetric connection - it actually gives me a better result than the web speed test which I assume is limited by Javascript performance.
- fatbas202 7y agoWas just looking through the thread for this comment. Because of this issue, I spent an obscene amount of time trying to diagnose a network problem that didn't exist when I upgraded to 1Gb. Hopefully others can avoid the same mistake.
- felipelemos 7y agoHe locked all above issues.
- metalliqaz 7y agothis project is the first time i've ever seen this kind of thing in problem reports. i've already seen enough to stay far away from that software.
- pekim 7y agoClosing the issues with an explanation of some sort would be one thing. But closing and locking them without any explanation is very strange. It makes it very difficult for anyone with the same problem to find any sort of explanation.