It’s essentially the same process as the download test but in reverse. Once the client determines it has the correct connections to test your internet service, it downloads additional chunks of data, measures the amount downloaded in the time allotted, and presents a download speed. The speed limit hasn’t changed, but more cars can pass through the same space at a faster rate thus, the 50th car will arrive sooner using a four-lane highway than it would on a two-lane.
Opening additional connections is like adding more lanes to the highway. Imagine your internet service as a highway with a speed limit. The general idea is to tax your internet connection and see how much it can do simultaneously. If the client detects you have room to spare, it opens more connections to the server and downloads more data. At this point, two things are measured: how long it took to grab the fragment of data, and how much of your network resources it used. The client opens multiple connections to the server and attempts to download a small piece of data. The test measures that roundtrip in milliseconds.Īfter the ping is complete, the download test begins. With the test server in place, the Speed Test sends a simple signal (a ping) to the server, and it responds. Some versions, like Ookla’s, have an option to change the server.
First, the client determines your location and the closest test server to you-this part is important. When you start a speed test, multiple things occur. How a Speed Test Works After you choose a server, a ping, download, and upload test is performed. For instance, our local ISP offers a plan with a 500 Mbps download speed, but 125 Mbps upload speed. Usually, the download speed features prominently, but if you dig into the details, the ISP typically specifies a slower upload speed for each level. Measuring the latter two is essential because most ISPs make separate promises for download and upload speeds. A Speed test measures your ping, and download and upload speeds.
0 kommentar(er)
