What part of KC you in? I grew up in midtown, 30th and Charlotte, Warwick, Virginia, etc.
Fred.
Why don't you two bytch nikkaz get a roomI grew up in the Northeast area but we moved north of the river when the Kansas City school accreditation fiasco started. I've bounced around from downtown to Westport but I'm back up north now
WHY IS NOBODY TALKING ABOUT THIS?!?!?!?!?!?!
Google Fiber gets formal launch, adds Google Fiber TV (update: event video) -- Engadget
Where them 1000mbps speeds though
A bit is an eighth of a byte
It's gigabit speed not gigabyte
so 125 megabytes per second is the top of what they're claiming basically
So they're saying users will have what? 125 MB/s? or 125 mbps?
There is a common misunderstanding, not just in the backup world, but in general about the difference between a MegaByte (MB ) and a Megabit (Mb). The main cause of the problem is the fact that all data storage is quoted and referenced in Bytes (KB , MB, GB , TB , etc) and network transfer speeds are rated in bits (Kb, Mb, Gb, etc).
You will see two speeds referenced in this article, "Mbps" and "MBps", they mean:
Mbps = Megabits per second
MBps = MegaBytes per second
In order to better understand this, we already know this:
1 Byte = 8 bits
Therefore, if you have a Gigabit (or GigE) network, the top speed of GigE is 1,000 Mbps (Note "Mb" and not "MB"). That equates to 125 MBps because:
1,000 ÷ 8 = 125
Due to additional bits that are needed to actually send data out on the wire for routing purposes, the number of bits used for network traffic is closer to 10 bits for every Byte. Therefore a GigE network would have a realistic top speed closer to 100 MBps instead of 125.
1,000 ÷ 10 = 100
people are talking about "mbps" without the proper MB / Mb (aka Mbit) designations... some people might be expecting 1 gigabyte per second internet
a lot of media people don't even make the distinction so I'm guessing a lot of posters haven't figured it out