Hot answers tagged


ISPs often prioritize traffic to so that they can brag how fast their connections are, while in reality, they don't provide that much bandwidth. They're perfectly aware that most users will only check that site for confirmation. You also have to keep in mind that transfer speed relies both on the client and the server. In today's world most ...


In addition to the other reasons posted, TCP connections don't work well with large files when the bandwidth-delay product becomes large. Like on an otherwise fast connection to an island. See Wikipedia's entry on TCP tuning. So Speedtest can dump a small file through the connection at 95 mb/sec, but wget can only get 10 mb/sec on a 20 MB file.


wget give good practical measure of the speed. The tests of Speedtest probably include kind of parallelism which can explain higher numbers. For good average speed test I think the time for download should be at least 90-120 seconds (to get good average)


wget is linked to OpenSSL whereas curl is linked to the NSS cryptographic libraries, which likely explains why they use different trust stores. I don't have a RHEL 6 system nearby but probably rpm -ql nss will show a different/additional trust store compared to what OpenSSL uses. This Red Hat resource may be of relevance


Amazon Linux does not update packages regularly. I've found I need to download source and build software a lot more on Amazon Linux / AL2 than Ubuntu, Centos, or Red Hat. The Amazon Linux package repository packages are usually out of date. I don't even bother with them for some software any more - Nginx, Apache, Fail2ban. I do use the Amazon repository for ...


One reason could be that often the maximum speed cannot be reached by just a single TCP connection. recently introduced a single connection mode. Try this and see if it makes a difference. Then, for the download use for example aria2 with parameters to use multiple conections and compare. e.g. aria2c -d /dev -o null --allow-overwrite=true --...


You don't necessarily need to go via the package manager, as long as you know which version goes where. The GNU wget source tarball + compilation instructions can be found here: If this is your first time compiling software, try it on a separate computer or VM first - preferably one with the same OS ...


Use , this is a Netflix based speed test meaning it cannot be differentiated by ISP's from Netflix itself. This is a more accurate test than any other test generally. People won't be worried about how fast a webpage loads, but rather how quickly the videos buffer due to the increased bandwith necessary to display a video. ISP's often ...


I just spent some time trying the above answers (adding newlines, deleting newlines, etc.) on a system running cronie. Finally found there is a bug in cronie 1.5.3 that only executes the first cron job for each user. It's fixed in 1.5.4 Hope this saves someone some time...


Check out the bash tool pacwget that does this using the pacparser library. It also robustly tries all combinations of proxies and servers.

Only top voted, non community-wiki answers of a minimum length are eligible