# New Speedtest Addon Wiki Page! **URL:** \ **Category:** Add-Ons\ **Created:** [30 November 2019 21:05 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470 "2019-11-30T21:05:49Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\ **Post date:** [30 November 2019 21:05 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/1 "2019-11-30T21:05:49Z")
There is a ![new](https://community.ipfire.org/uploads/default/original/1X/ffb2eb37e6c49a2a7290a9c612fd85c5b7ec6a47.png) wiki page for a new addon - [speedtest](https://wiki.ipfire.org/addons/speedtest-cli). The new addon was released as part of [Core Update 137](https://blog.ipfire.org/post/ipfire-2-23-core-update-137-released). Feel free to comment or add to it. ---
**Author:** ![yoda](https://community.ipfire.org/user_avatar/community.ipfire.org/yoda/32/332_2.png) [@yoda](https://community.ipfire.org/u/yoda)\ **Post date:** [30 November 2019 21:34 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/2 "2019-11-30T21:34:51Z")
Hi @jon, I was just testing out speedtest via the console and comparing the results to those received from running speedtest in a browser. There appears to be a wide discrepancy and I was wondering if you also experience this and have any idea why that might be? > Avg Down/Up (Mbps) > Console: 340 / 21 > vs. > Vivaldi: 635 / 21 I’m using the same server for all tests and I switch back and forth from the console and browser. The console consistently shows 340 while the browser holds steady around 635. ---
**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\ **Post date:** [30 November 2019 22:32 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/3 "2019-11-30T22:32:19Z")
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](https://github.com/sivel/speedtest-cli) ---
**Author:** ![yoda](https://community.ipfire.org/user_avatar/community.ipfire.org/yoda/32/332_2.png) [@yoda](https://community.ipfire.org/u/yoda)\ **Post date:** [30 November 2019 22:42 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/4 "2019-11-30T22:42:11Z")
Just an FYI, it appears that speedtest-cli cannot really be relied upon for accurate results…from: [https://github.com/sivel/speedtest-cli](https://github.com/sivel/speedtest-cli) > _" There is the potential for this tool to report results inconsistent with [Speedtest.net](http://Speedtest.net). There are several concepts to be aware of that factor into the potential inconsistency:_ > > _1. [Speedtest.net](http://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](http://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."_ ---
**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\ **Post date:** [30 November 2019 23:21 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/5 "2019-11-30T23:21:28Z")
Good find! ---
**Author:** ![ms](https://community.ipfire.org/user_avatar/community.ipfire.org/ms/32/16615_2.png) [@ms](https://community.ipfire.org/u/ms)\ **Post date:** [1 December 2019 20:41 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/6 "2019-12-01T20:41:13Z")
That is obviously a normal problem that you have when benchmarking something. So this speedtest is just as reliable as any other ones. But they are reproducible, easy to run and give a good idea about where you are ending up. ---
**Author:** ![hellfire](https://community.ipfire.org/user_avatar/community.ipfire.org/hellfire/32/8454_2.png) [@hellfire](https://community.ipfire.org/u/hellfire)\ **Post date:** [2 December 2019 17:05 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/7 "2019-12-02T17:05:33Z")
So is speedetest limited by IPfire QoS or not? Edit: it seems so, at least a test revealed this. Question: is there a cmd to stop QoS while running the speedtest and restart it afterwards? ---
**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\ **Post date:** [3 December 2019 00:02 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/8 "2019-12-03T00:02:59Z")
Something besides the IPFire WUI menu **Services** \> **Quality of Service** , then click **Stop**? I see a command `/usr/local/bin/qosctrl`. I’ve not used it before so I really don’t know if this helps. ```auto [root@ipfire ~]# /usr/local/bin/qosctrl No argument given. qosctrl (start|stop|restart|status|generate) ``` **EDIT** : see [https://forum.ipfire.org/viewtopic.php?f=27&t=20266](https://forum.ipfire.org/viewtopic.php?f=27&t=20266) ---
**Author:** ![ms](https://community.ipfire.org/user_avatar/community.ipfire.org/ms/32/16615_2.png) [@ms](https://community.ipfire.org/u/ms)\ **Post date:** [3 December 2019 11:21 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/9 "2019-12-03T11:21:40Z")
> [@hellfire](#): > > So is speedetest limited by IPfire QoS or not? Yes, that is the job of the QoS, to limit certain traffic. ---
**Author:** ![hellfire](https://community.ipfire.org/user_avatar/community.ipfire.org/hellfire/32/8454_2.png) [@hellfire](https://community.ipfire.org/u/hellfire)\ **Post date:** [3 December 2019 11:49 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/10 "2019-12-03T11:49:13Z")
I know, Michael, however, when executing speedtest on IPFire’s console, I thought this would probably not be affected by QoS. Anyway, I’ve already found that QoS interferes there, too… Thx, Michael ---
**Author:** ![pike\_it](https://community.ipfire.org/user_avatar/community.ipfire.org/pike_it/32/16425_2.png) [@pike\_it](https://community.ipfire.org/u/pike_it)\ **Post date:** [3 December 2019 12:10 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/11 "2019-12-03T12:10:45Z")
So… two options: - disable QoS while testing - do not speed test Latter is not that useful… Could a Qos rule override Qos management for speed test _starting from IPFire_? ---
**Author:** ![hellfire](https://community.ipfire.org/user_avatar/community.ipfire.org/hellfire/32/8454_2.png) [@hellfire](https://community.ipfire.org/u/hellfire)\ **Post date:** [3 December 2019 16:22 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/12 "2019-12-03T16:22:25Z")
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. ---
**Author:** ![ms](https://community.ipfire.org/user_avatar/community.ipfire.org/ms/32/16615_2.png) [@ms](https://community.ipfire.org/u/ms)\ **Post date:** [3 December 2019 17:33 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/13 "2019-12-03T17:33:58Z")
Sorry, I am completely missing what you are trying to do here. Why do you need to run the speedtest once every night? ---
**Author:** ![pike\_it](https://community.ipfire.org/user_avatar/community.ipfire.org/pike_it/32/16425_2.png) [@pike\_it](https://community.ipfire.org/u/pike_it)\ **Post date:** [3 December 2019 18:24 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/14 "2019-12-03T18:24:08Z")
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” ---
**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\ **Post date:** [3 December 2019 19:15 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/15 "2019-12-03T19:15:35Z")
Hey! I just came across this while looking for something else. Ookla came out with their own Speedtest CLI. Much more better™ then the sivel version. [https://www.speedtest.net/apps/cli](https://www.speedtest.net/apps/cli) Installed on my iMac: ```auto 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. **EDIT** : [https://www.speedtest.net/insights/blog/introducing-speedtest-cli/](https://www.speedtest.net/insights/blog/introducing-speedtest-cli/) ---
**Author:** ![pike\_it](https://community.ipfire.org/user_avatar/community.ipfire.org/pike_it/32/16425_2.png) [@pike\_it](https://community.ipfire.org/u/pike_it)\ **Post date:** [3 December 2019 19:19 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/16 "2019-12-03T19:19:39Z")
Pro for Ookla: widely know, quite “acceptable” for non-tech people. Pro for sivel: it’s independent (and maybe not twekable) by Ookla ---
**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\ **Post date:** [3 December 2019 19:41 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/17 "2019-12-03T19:41:08Z")
> [@pike\_it](#): > > you can bug your ISP asking “Please improve my service” This is/was the article I was looking for: [I set up my Raspberry Pi to automatically tweet at Comcast Xfinity whenever my internet speeds drop significantly below what I pay for](https://www.reddit.com/r/technology/comments/43fi39/i_set_up_my_raspberry_pi_to_automatically_tweet/) > **[AComcast User (@A\_Comcast\_User) on X](https://twitter.com/a_comcast_user)** > > I tweet when my automated xfinity speedtest shows speeds significantly lower than what I pay for. Made with a Raspberry Pi and python. 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) ![54%20PM](https://community.ipfire.org/uploads/default/original/1X/012ed553ae0127dbe65e6e3ce6a44740c9085c3a.jpeg) ---
**Author:** ![hellfire](https://community.ipfire.org/user_avatar/community.ipfire.org/hellfire/32/8454_2.png) [@hellfire](https://community.ipfire.org/u/hellfire)\ **Post date:** [4 December 2019 11:45 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/18 "2019-12-04T11:45:40Z")
Jon, so you are using speedtest-cli as a base for this graph? _I plan to do the same as mentioned above._ ---
**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\ **Post date:** [4 December 2019 17:10 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/19 "2019-12-04T17:10:01Z")
Yes. But running on a Raspberry PI and a 100 MB ethernet port. So the max download speed was near 92. ---
**Author:** ![yoda](https://community.ipfire.org/user_avatar/community.ipfire.org/yoda/32/332_2.png) [@yoda](https://community.ipfire.org/u/yoda)\ **Post date:** [6 December 2019 06:32 UTC](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470/20 "2019-12-06T06:32:22Z")
@ms Why did you remove from [https://wiki.ipfire.org/addons/speedtest-cli](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. [Next page](https://community.ipfire.org/t/new-speedtest-addon-wiki-page/470.md?page=2)