Speedtest CLI brings the trusted technology and global server network behind Speedtest to the command line. Built for software developers, system administrators and computer enthusiasts alike, Speedtest CLI is the first official Linux-native Speedtest application backed by Ookla.
Our mission at Ookla is to make the internet better and faster for everyone by providing data and insights on real-world internet performance and quality. With billions of tests and coverage scans worldwide, we meet you where you are with apps for the devices you use most.
The highest speed you will see is the maximum speed that your connection and the server's connection can offer. If your connection is 512KB and the place where you are downloading is 400KB, your max connection will be 400KB because it is the max for the server you are downloading from.
You need to have at least 4 or 5 different testing sources to have a more accurate speed. Never test only from the same site as this can be affected by your distance to it, any problem in the server and the connections to it, etc. Always test from different servers.
Actually, Ookla, the provider of Speedtest released a command-line utility that is measuring your speed against a huge number of servers spread around the world. You can find instructions on how to install it on this link and you can use it fairly simple by executing:
where -s sets the server ID against which you want to test your Internet speed, -f is defining the format of the output. I think the most useful information is generated when you use json/json-pretty format for the output because a lot of the information of the test setup isn't printed if you are using the csv/tsv format. Both -s and -f are just optional but if you want to automate your measurement they might be useful.
It's a more generic solution that can be consumed by other applications. I managed to pinpoint an ISP network issue with it that resulted in doubling my SFTP downstream speed, which resulted in increased happiness.
Perhaps you want to check that your network speeds match up to what you pay your ISP for, or see if a connection issue currently bugging you is real or imagined. Whichever; being able to run an internet speed test from the command line is handy, and easy to do.
I use a Python tool called speedtest-cli to test internet speeds on Linux. This uses the speedtest.net website mentioned at the start of this post. Using this you can test your internet upload and downloads speeds, and measure ping.
If you want to see more information about your network during and after the test (such as IP address, test location, etc) you can run speedtest-cli without the --simple flag. This delivers more verbose output, like so:
How do you prefer to do network speed tests? Does being able to do it from the command line instead of a dedicated network test website appeal? Share your thoughts on this tutorial down in the comments section!
This requires a few extra steps as we will need to add the official Ookla repository to our device. However, one of the most significant advantages of using the official repository is that you will always have the latest software version.
This command line interface allows you to test the internet speed of your Ubuntu devices network easily. Additionally, you can test this against multiple servers to check how your internet performs when connecting to certain locations.
A situation often arises when you need to determine the bandwidth of the Internet channel. In the desktop version of the operating system, it is enough to enter the corresponding request into a search engine and measure the speed on any of the search results sites. But if it needs to be done in the server version, the method will be different. In this tutorial, we are going to take a look at how to test Internet connection speed on Ubuntu 20.04. All commands must be run as root.
With the increase in people staying at home and spending more time on the Internet, ISPs have seen traffic loads higher than ever. If you noticed your network speed was slower at times, this global overload is the reason.
The tools in this guide help you check the Internet and LAN speed on a Linux machine. The article uses Ubuntu 20.04 for instructions, but the utilities work for any Linux distribution.
While it's not listed in the man page of openssl speed, it can still measure aes speed (on my machine at least). Running openssl speed some random value will print an error message that includes the list of ciphers it can test.
If you want to test the speed of disk encryption algorithms, you can also use cryptsetup benchmark, which will show you the speed of different encryption algorithms and modes in bytes/second. You'll notice that the mode can influence speed quite a bit (on my machine, aes-xts is three times as fast as aes-cbc).
On my system (i7 4GHz) the results of cryptsetup benchmark gives AES256-CBC at about 600MiB/s for encryption and 2.1GiB/s for decryption, and AES256-XTS (when using XTS, the key is split in half so you have to look at the 512bits key result for AES256) at about 1.8GiB/s for encryption and 2GiB/s for decryption. As you can see, that's much faster than the speed of even a good SSD, and certainly a lot faster than even an excellent typist.
You can run OpenSpeedTest Server in your Home Lab, Office Server or Cloud Server. So that you or employees who work from home can run a speed test to your office and make sure they can run everything smoothly.
Choosing between ISP1 & ISP2.Sometimes your ISP2 is Faster than ISP1 when you test your speed on popular speed test sites. But when you connect to your Home/Office/Cloud, that slower connection may perform better. The only way to find out is to run a speed test against your infrastructure.
Troubleshooting network issues.It is common even when your Internet connection is working fine, but some of the devices in your network may experience trouble getting decent connectivity to the internet. The issue might be the wrong VLAN ID or Faulty Switch. If you run a Local network speed test, you can find and fix these issues easily.
Before you add a repeater.Most repeaters will reduce your network speed by 50%, so if you put it far away, it will perform worse, and if you put it too close, you will not get enough coverage if you run a Local Network speed test. Depending on the application requirements, you can decide exactly where you need to put your repeater.
Browsing experience.Many useful browser extensions are out there that we all know and love. But some of them are really slowing you down for a few seconds per page you visit. You may see good performance when you test your network performance via File Transfer or Command-line utilities, but you may experience poor performance when browsing the internet. This is due to a bad browser configuration that includes unwanted extensions installed. From my experience, only keep the one you are going to use every single day. Extensions that you may use once in a while should be removed or disabled for maximum performance. If you see poor performance, try OpenSpeedTest from Private Window or Incognito Window. This tool can be used to check the browser performance and impact of Extensions on your browsing experience.
It only takes a few seconds to do a test, and it returns the transfer size and calculated bandwidth. I ran a few tests from my PC and my laptop, using my home server as the server machine. I recently put in Cat6 Ethernet around my house, so I get up to 1Gbps speeds from my wired connections but much lower speeds on WiFi connections.
You may notice where it recorded 16Gbps. That was me using the server to test itself, so it's just testing how fast it can write to its own disk. The server has hard disk drives, which are only 16Gbps, but my desktop PC gets 46Gbps, and my (newer) laptop gets over 60Gbps, as they have solid-state drives.
Knowing the speed of your network is a rather straightforward task with these tools. If you prefer to script or run these from the command line for the fun of it, any of the above projects will get you there. If you're after specific point-to-point metrics, iPerf is your go-to.
iPerf involves no writing to the disk, all test data is only ever in memory. Those devices performing better just happen to have better CPU performance to be able to better shuffle the packets around.
One thing to keep in mind is that the client is sending by default on iPerf. If you want, you can use the -R option to have the server send instead, to test against these public iPerf servers, in the downstream direction.
I'm trying to setup an Ookla server for speed test. My OS is Ubuntu (20.04 LTS) and I installed the script, also set it up to start after reboot, but I don't know how to set it up to work with HTTPS. The test page says my server passed on netgauge, websocket and crossdomain but failed on https. I would also like to know how I use my server for speed testing before I upload it to Ookla? I would like to know what is the speed and how it performs. I didn't find much documentation on Ookla's website, for example I didn't find how to setup HTTPS. If I get a certificate from Let's encrypt, how do I install and use my certificate?
Please note that the automatic Let's Encrypt certificate provisioning will not begin until after your server has been submitted and either approved or accepted for use. The HTTPS test on the Server Tester can be ignored during the initial submission period.
"(...) 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. (...)"
31c5a71286