Download Speed Test Command Line
Maggie Schnair
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.
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.
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.
I would like to write my own local speedtest script with a server script for listening to connections. To try and not duplicate my efforts, I haven't found much while searching. I can find lots of over-the-internet tests (sppeedtest, ookla) but nothing that I can hosted myself and check upload/download from a local machine on my local network to see what the bandwidth is like.
We've shown you how to test your internet connection speed using a web browser, but there are a few reasons you might want a command line tool instead. Maybe you're remotely connected to a server via ssh, and want to test speeds on that machine. Maybe you're already used to using commands to troubleshoot your network, and want to add a speedtest to your toolkit. Or maybe you just think the command line is cool. No judgement.
The simplest way to install speedtest-cli on a Mac is using Homebrew, the open source package manager for Mac. Check out our guide to installing Homebrew if you don't have it set up (if you use the command line a lot, you should absolutely install Homebrew).
You can now use speedtest-cli on Windows. Note that you could use pip to install speedtest-cli on Linux and macOS systems, but it's simpler to use the system-wide package manager for consistency's sake.
I found that Speedtest.net has a command line interface that you can install and run using "Command Prompt" if you're using Windows. What's cool about that is you can use Windows' "Task Scheduler" to run Speedtest.exe periodically and write the results to a .txt file (I used "cmd /c speedtest.exe >> speedtestlog.txt" as my script in Task Scheduler) I run mine regularly to check my speed, and see how it changes over time. (Mine bogs down during the day on weekdays - go figure!) Also, I need to figure out a way to timestamp the entries. I hope this helps you out. Cheers!
I'll check out Centrastage... looks complex. Doesn't seem like something that could quickly and easily be used by your clients. Why not just send them to TestMy.net? Why do you necessarily need a command line program? I'll be happy to put one together for you... actually one of my first tests was a simple command line program, I think it would be fun to put that together.
and this is were if can get annoying for the users who are busy and then theres me wanting to do a speedtest,so to be able to do one in the background (without them knowing) is ideal and like i said i can use WGET but doesn't really give me the results as i want to see then (unlike a flash component)
What's a command line? Haha. I haven't used used it since running a VT100 terminal emulator on a Mac IICi in the early 90s, to access a MicroVax and an IBM 370 at GE. I take that back, I used the Terminal app on my iMac a while back to try something I saw posted in another discussion forum.
The first programming I ever did was on an HP9825, with a single line display. HP's HPL language. OMG.... p(p1,p3,p4(p2,p5)). We used them at GE to control some of the first IEE-488 automated instruments that tested our electronic controls for jet engines. Software QA was not too good in the early days. You just took a Sharpie, and wrote on the tape cartridge or big floppy disk "this is the latest version" ...HAHAHAHA
very true and really not to hard to do... but I think it could be done without additional software. I've written many simple bash scripts that do that... part of my roots with speed testing was command line. I just never shared it with anyone.
Yeah, I would try to make it in a way that could be run from any command line... regardless of operating system or software installed. You know me... that's always my aim. Because I personally wouldn't want to have to fart around with installing things to make a simple test work... you really shouldn't have to.
I don't know how I'm going to make it yet or when I can start but I will make it a project of mine to come up with a command line option. I have a few interesting ideas for how I could do it... We'll just have to see what I come up with. I have a lot of work on the table right now. If one of you could just give me a million bucks so I get build a team of developers to build some of the pieces of my puzzle, that would be cool.
I'm interested in this too. I'd like a way of automating speed tests from various locations to keep stats on network availability. I may experiment with phantomjs, but would prefer to use something smaller or natively executable on standard linux configs.
That is one of my favourite features - if I ever need to do a speedtest from a device that has no GUI ( -something-is-seriously-broken-in-the-apple-desktop-developer-world/?p=346473) I can use that option, which is super handy.
We have all used tools like speedtest.net to test upload and download speeds. Whether it was to test the WiFi in that coffee shop (I use my own tether, never unknown hot spots), preparing for a LAN party (do people still do that?), or just a step in troubleshooting, we have all been there. For one reason or another you simply think you are being cheated of bandwidth, so you want independent verification of your speeds. This typically means opening a browser and going to a website to test your connection. But what if you want to run a speed test on a remote server? In this article we will discuss running an internet speed test from the Linux command line, and skipping the browser.
There is something about the raw efficiency of the command line that I am really attracted to. As I discussed in the article "5 Command Line Tool to Break Your Dependence on the GUI", I try my best to stay away from the browser. It usually creates an unnecessary distraction. The internet is designed to grab your attention like a laser pointer does to a cat. So let's get started, and figure out one more way to stay away from the GUI.
There are a few different tools you can use to run a speed test from the command line. To make things even more confusing the two most popular share the same exact name, but both use the speedtest.net service.
The second tool is built by Ookla, the people who bring you the speedtest.net website and service. Installing it requires you to add a repo for your package manager. But the maintainers offer simple instructions for installation.
Ookla's speedtest is also a little easier on the eyes. It spreads the information out which makes it easier to read and displays a neat little progress bar. A URL you can use to share the results is also displayed by default.
In this article we cover how to run a speed test from the command line using two similar tools. The unofficial python script and the official Ookla Speedtest CLI. We discussed installing, using and setting options for each one. This should be enough to get you started.
Important to note: You cannot have speedtest-cli and the official speedtest package installed at the same time on a Debian based distro. I am not sure about other distros but this is the reason why...
Effectively zero latency on both the source and the destination. I'm pretty sure that cachefly has more than enough bandwidth to allow this to be a certain measurement of my local pip. Also, it doesn't do anything that my ISP could detect as a speed test. That makes me feel more secure.
If you want to install this on Rocky Linux, you'll need to apply this patch to *install.rpm.sh* So download it by dropping the " sudo bash" from the first line, modify the script, then "sudo bash install.rpm.sh", then "sudo yum install speedtest"
I compared speedtest-cli to speedtest.net on a modern browsers. The numbers are similar, but not the same. If you read the output for speedtest.net on a browser, the ping server that speedtest.net uses is very close to your present location. I think modern browsers are good at guessing your location. The ping server that speedtest-cli chooses is not as close as that of speedtest.net. Perhaps that is why the numbers are not the same.
To execute a TCP connect test, specify the port number. The followingcommand executes connect attempts against the target as quickly aspossible, only printing a summary when finished with the 100 iterationsand 1 warmup iteration:
This command tests bandwidth to a PsPing server listening at the targetIP address for 10 seconds and produces a histogram with 100 buckets.Note that the test must run for at least one second after warmup for ahistogram to generate. Simply add -u to have PsPing perform a UDPbandwidth test.
Do you plan to use the Terminal window on your Mac to perform network speed tests, or will you continue using the flashy dedicated websites? Be sure to let us know your choice and reasoning in the comments section down below.
Thank you for sharing this! It's both interesting and very simple. But for typing practice, I always use wpm online typing test site since it offers one minute, three minute, and five minute tests. and yes result of typing speed can be accessed at any time in the notification center
I'm having difficulties getting the notification to show. The debug menu indicates that the Speedtest succeeded and I can see the speeds for upload and download. However no notification. I'm on an M1 iMac. Any ideas?
df19127ead