With 1 Gbps, most ISPs and router manufacturers mean 1000 Megabits per second. And this site also shows the speed in bits per second. So, the speed shouldn’t really be more than 1000 Mbps or 1 Gbps because their hardware isn’t capable of that, even if their ISP is providing some extra speed (which sometimes they do, especially with servers like Netflix).
This is the typical wrong speed reported by Fast.com and that’s why people shouldn’t use it to measure how fast their connection is, unless they are trying to verify if their connection sucks with Netflix servers and/or video streaming.
I think they’re getting at the difference between using powers of 10 vs powers of 2.
So 1 kb (kilobyte) = 10^3 = 1,000 bytes, but since computers tend to use powers of 2, sometimes they might use 1 kb (kibibyte) = 2^10 = 1024 bytes
Strictly speaking, kilo always means 10^3, and kibi always means 2^10 so they’re not equal. But in common parlance, the difference barely matters so it is common to use kilo- even when kibi- is strictly correct.
The same holds true for bigger prefixes like giga (10^9) and gibi (2^30).
So I think that guy was getting at those differences even though the number he said makes no sense even if you account for the giga/gibi difference. So maybe I wrote all this for no reason lol
I feel like you’re referring to the 1000 vs 1024 issue, but to get that kind of factor you’d need to be talking on the order of 10^27 bits per second since 2^90 / 10^27 = 1.2379
Fast.com uses a crude way to determine speed. It’s obviously some flawed math formula since I’ve gotten some wild speeds before (like over 6-7Gbps) on a 2Gbps connection. Whatever it is is obviously inaccurate.
1 Gbps is computationally 1.24416.
This is it
With 1 Gbps, most ISPs and router manufacturers mean 1000 Megabits per second. And this site also shows the speed in bits per second. So, the speed shouldn’t really be more than 1000 Mbps or 1 Gbps because their hardware isn’t capable of that, even if their ISP is providing some extra speed (which sometimes they do, especially with servers like Netflix).
This is the typical wrong speed reported by Fast.com and that’s why people shouldn’t use it to measure how fast their connection is, unless they are trying to verify if their connection sucks with Netflix servers and/or video streaming.
Except you know overhead is a thing
Care to explain?
I think they’re getting at the difference between using powers of 10 vs powers of 2.
So 1 kb (kilobyte) = 10^3 = 1,000 bytes, but since computers tend to use powers of 2, sometimes they might use 1 kb (kibibyte) = 2^10 = 1024 bytes
Strictly speaking, kilo always means 10^3, and kibi always means 2^10 so they’re not equal. But in common parlance, the difference barely matters so it is common to use kilo- even when kibi- is strictly correct.
The same holds true for bigger prefixes like giga (10^9) and gibi (2^30).
So I think that guy was getting at those differences even though the number he said makes no sense even if you account for the giga/gibi difference. So maybe I wrote all this for no reason lol
You are still appreciated.
I feel like you’re referring to the 1000 vs 1024 issue, but to get that kind of factor you’d need to be talking on the order of 10^27 bits per second since 2^90 / 10^27 = 1.2379
Thankyou for being able to do math. Seriously.
No, it’s not.
https://en.wikipedia.org/wiki/Data-rate\_units#Gigabit\_per\_second
Idk why that comment is getting upvoted so much.
Fast.com uses a crude way to determine speed. It’s obviously some flawed math formula since I’ve gotten some wild speeds before (like over 6-7Gbps) on a 2Gbps connection. Whatever it is is obviously inaccurate.
Except its not…and even if you’re trying to talk in Gibibytes, its still not.