Speedtest 100 100

[Arnold Gilgen]

Whatis FAST.com measuring? FAST.com speed test gives you an estimate of your current Internet speed. You will generally be able to get this speed from leading Internet services, which use globally distributed servers.

Why does FAST.com focus primarily on download speed? Download speed is most relevant for people who are consuming content on the Internet, and we want FAST.com to be a very simple and fast speed test.

How are the results calculated? To calculate your Internet speed, FAST.com performs a series of downloads from and uploads to Netflix servers and calculates the maximum speed your Internet connection can provide. More details are in our blog post.

What can I do if I'm not getting the speed I pay for? If results from FAST.com and other internet speed tests (like dslreports.com or speedtest.net) often show less speed than you have paid for, you can ask your ISP about the results.

Hey there, do you see any problems when you run speedtest manually from the command line as the netdata user? (This needs to be done once manually to accept the license agreements. You probably know this from the blog already.)

The idea being that this would be fine to run every 30 mins and then over a few days and weeks be useful for monitoring isp speed etc while not actually eating into your bandwidth. Typically it would not really make sense to run it at much more frequent intervals below maybe 10 or 15 minutes.

So if you are on an unlimited connection on a raspberry pi and are OK to have speedtest download and upload a bunch of data then setting the speedtest_update_every variable in the speedtest.conf file to a smaller value should do the trick.

Might I suggest that a compromise might be an RFC to enable displaying of time-series data with custom sampling intervals via the custom dashboards feature? That way no major changes would probably have to be made to the code for the main overview and node views but would allow people to build out and display their data.

If you have done both of the above, then I think the problem is due to the path that this script community/install-collector.sh at main netdata/community GitHub is using while copying the collector code. Please verify if the path used is different from the Netdata path on your system, if yes then you can either update the script or do the steps manually.

I have also followed the steps in How to monitor Internet quality and ISP performance with Netdata Netdata Blog, but it does not seem to work. Looking at my network load in Task Manager, I can see no load great enough to be a speed test when Netdata is running.

I have a MX84 which we have just had our leased line upgraded to symmetrical 500MB, speedtest we're getting 250MB, so i got the ISP to come on site to run tests, connecting his laptop direct into the circuit. After a while they removed restrictions and had to boost the line to get the 500MB speed. We then reconnected the MX and did a speed test which still is 250MB speed.

Hi Richard,

Refer to 1.png and 2.png, you may press on that little bell icon and you will see the release note.

Currently, only Venus IC2 is running v2.11.0. Earth IC2 and Mars IC2 are still on v2.10.0.

For the speedtest feature you mentioned, it needs the combination of IC2 v2.11.0 and Balance firmware v8.3.0. As of now, firmware v8.3.0 is still under development. Thanks.

Attachments:

Hello Peplink Team. A loolonnnggg time coming - THANK YOU!! The new flash indicates it should be there now but I can not find the setting in IC2 nor fw v8.3.0. If you could point us in the right direction, that would be extremely helpful.

And even then, since most people test with speedtest.net on their devices rather than iperf, you also want the speedtest client and tests for latency. And then you want notifications when a device that was speed testing well no longer is.

Thanks Martin and though I retired three years ago I still try to keep my head in the game and keep up on things. It would be nice to see this feature made available for the benefit of other users and check it off.

Here is why I need it. I remotely manage an RV park that is 5 hours away. I have 3 internet connections on a Balance router. I need to be able to test the speed of each internet connection individually. I need it to tell the router what the upload and download bandwidth is so that it will distribute traffic accordingly, and two, to see how much my providers are throttling my connection.

but later on I have enabled ssl decryption for testing purposes, hoping that the app will be correctly identified byt the firewall, however it did not work, palo alto still sees speedtest .net as pure ssl traffic

Hi, since a couple of days my speedtest thing based on the network binding addon keeps being offline. It worked very well in the last 2 months. I was wondering if this has to do with the address i am using. If i download the speedtest file from the browser, this still works.

you can check the available serverlist via speedtest-cli command

speedtest-cli --list displays a list of speedtest.net servers sorted by distance

and / or of course:

speedtest-cli --list grep -i germany the currently accessible german servers

"(...) I just setup Ubuntu on my new PC. For testing purposes I installed the speedtest-cli and with the command Speedtest everything worked fine. I don't know what I did then, but now I am getting an http error 403 forbidden. But when doing speedtest --secure everything works fine again. (...)"

Thanks, Ricmarques, but my question is why we need add "--secure"?

I didn't do anything, I just reinstalled my PC, and then speedtest-cli can't work. And I must added "--secure" now, it's so wierd! This problem wastes my half day time. Why without "--secure" option, my original environment could work? The root cause is on the different version of "speedtest-cli"? I suspect so.

Thanks for --secure.

I have only headless Debian and I noticed that speedtest with no secure was working yesterday with no error. Today I tried it with the error but --secure worked nicely.

What changed since yesterday is a new kernel published in apt repo.

After upgrade speedtest (no secure) started working as usual. Is that coincident?

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?

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

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.

@ms Why did you remove from -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.

First let me start to say that running speedtest from a pfSense box should not be best practice for business use. And trouble shooting on a business implementation should not need this widget. However for the home user that understands that he is using all his bandwidth during the test and puts strain on the pfSense box CPU during the test as well. Having a quick way to test from the pfSense box it is fine to have this feature. And yes i am aware that most of the time you want to run a test through pfSense from a client on your LAN but that does not validate the reason to deny people the choice to have the function on pfSense.

I made a widget (open source ofcourse) that you can install together with the official speedtest-cli from speedtest.net. So you can run a speedtest with just one click on your pfSense dashboard. There is a full install and uninstall instruction available so you can remove it again if it is not wat you want after you tested it.

I already mentioned it in the original post at the very beginning, so yeah i agree with you that you should use this function with care. I made it because some home users like me have parts of their internal network (wifi far from the access points in my case) slower then their internet (1Gbit fiber in my case). And i have had issues with the ISP and want to do a quick test from my phone for example that is not capable of testing above 500Mbit even when next to the accesspoint. In a business case i would only use this during initial setup or troubleshooting and you are required to test from the router for some odd reason. If there is no real need to hit the test button i recommend not trigger the test, the wiget will show the last recorded test in that case. I also will not build any cron task or anything that will test at set intervals, if you really need to do that i recommend setting up something from a proper client. I do disagree that this test give inconsistent results, the used original test uses far less cpu resources then the non official speedtest-cli that is broken anyway. I can confirm that a single core vm running on a i7-3770 (a cpu from 2012) can test a 1Gbit connection just fine. If you have less horsepower as a single core of a 12 years old processor and faster internet connection then you will have more performance issues anyway.

I'm encountering a strange problem here.On my local homeserver(Debian 9.9), speedtest-cli and it's python pendant are freaking slow.Since I use it to monitor my ISP connection stability, this is a problem.

I was messing with this - and have speedtest-cli and speedtest++ installed. (Unfortunately, my GUI PCs are behind a homeplug connection, but trust me when I say the rest). Its probably down to the protocol that's being used.

3a8082e126