I turned off the IPFire QOS (menu Service > Quality of Service) and gave things a try.
This is the speedtest addon running on my IPFire box:
ping: 17.541 ms
Download: 181.33 Mbit/s
Upload: 12.07 Mbit/s
This is the speedtest-cli running on the console on my Mac:
ping: 17.015 ms
Download: 182.24 Mbit/s
Upload: 12.15 Mbit/s
I’m not a Vivaldi user but the test results for Safari running on my Mac:
ping: 11 ms
Download: 239.56 Mbit/s
Upload: 12.01 Mbit/s
And here is the Speedtest app loaded on my Mac:
ping: 11 ms
Download: 241 Mbit/s
Upload: 12.1 Mbit/s
All tests are to the same server.
So I see similar odd results and they seem to point to Speedtest-cli. But I do not know why. Maybe the author could provide more clues than me. https://github.com/sivel/speedtest-cli
" There is the potential for this tool to report results inconsistent with Speedtest.net. There are several concepts to be aware of that factor into the potential inconsistency:
1. Speedtest.net has migrated to using pure socket tests instead of HTTP based tests 2. This application is written in Python 3. Different versions of Python will execute certain parts of the code faster than others 4. CPU and Memory capacity and speed will play a large part in inconsistency between Speedtest.net and even other machines on the same network
Issues relating to inconsistencies will be closed as wontfix and without additional reason or context."
Idea behind is to create a script that stops QoS at night, run the speedtest and restart QoS afterwards.
The result in CSV format should be inserted into a database for monitoring.
I will see if this works, reliable, besides the mentioned measuring inaccuracy.
Benchmark the provider during the days/weeks. Most of ISP are in overbooking
And having some stats for understand/know the real performance, QoS can be adjusted and you can bug your ISP asking “Please improve my service”
iMac3:~ me$ speedtest -s 5900
Speedtest by Ookla
Server: aFastServer - Arlington Heights, IL (id = 5900)
ISP: myFastISP
Latency: 10.95 ms (0.31 ms jitter)
Download: 240.29 Mbps (data used: 223.9 MB)
Upload: 11.98 Mbps (data used: 9.5 MB)
Packet Loss: 0.0%
Result URL: https://www.speedtest.net/result/c/bb62347f-3562-47f5-8277-1234567890
Note 1: This is with QOS turned off. Note 2: Be aware if you have the sivel speedtest installed. The sivel speedtest will continue to run instead of the Ookla speedtest.
After reading the above I started keeping track of Internet speeds. I was not looking for “blazing fast at all times!”. But when the speeds went low it made it easy to complain. (the breaks in the graph are when there was no Internet service)
@ms Why did you remove from https://wiki.ipfire.org/addons/speedtest-cli the quote from speedtest-cli Github page that provide users with a heads up about the potential for results inconsistency? I think this is very relevant to anyone who uses speedtest-cli.
sorry for not leaving a comment on this (I need to add that to the wiki when we do a rollback).
I thought that it would be better to either link this discussion or reference it elsewhere. I do not think that we need to have an extra paragraph on the wiki for this, because I consider these speed tests always as unreliable. Benchmarks are always flawed in one way or another. I highly doubt that this is because of the Python implementation.
Speed tests are just some kind of indication about what has gone through your link at a certain point in time. They are not reproducible at all.
I agree, however, for me, running IPFire in my home lab, speedtest-cli delivers enough information to get at least an impression what’s going on or if the speed decreases significantly over a a certain period of time.