3 ms·
Just to play devil's advocate. There's unit's miss-match here. The information transfer rate that would apply to physically moving a storage device would be bi
by joe_the_user 16y ago
Just to play devil's advocate.
There's unit's miss-match here. The information transfer rate that would apply to physically moving a storage device would be bits per second per meter (information-unit/time-unit/distance-unit). Bandwidth is normally measured with bits and seconds, with no distance unit. The two aren't directly comparable. If you somehow you had a 20 Kbs rate to Pluto, it would be a comparable information/time/distance transfer to a fully laden 747.
- jerf 16y agoAll that means is you need to add a distance conversion factor in, and it all works fine, albeit tied to that distance. And, lo: "Now assume it flies from San Francisco to London in 10 hours." The two may not be directly comparable, but that's ok, because they weren't directly compared. Defining the bandwidth of that specific flight is perfectly reasonable and no "devil's advocate" is needed. (And if you want to point out that this isn't a practically useful number... well, yeah. But it's perfectly well-defined and unit-correct.)
- guelo 16y agoThe missing measurement is latency. The ping times of IP over 747 are dreadful.
- Dove 16y agoI was thinking the same thing. The bandwidth of the 747 isn't a constant. It depends on the distance between the endpoints. If I want to transfer data 30 feet from one system to another, pulling the hard drive, tossing it onto a 747 rolling by on the runway, tossing it back, and then reinstalling just blows away any LAN ever built.