3 ms·
I find this a rather misguiding post. First off, do you really think it's more practical to ship data per airplane than a simple cable that's already connectin
by lucb1e 14y ago
I find this a rather misguiding post.
First off, do you really think it's more practical to ship data per airplane than a simple cable that's already connecting you? Not that bandwidth is completely for free, but most of the time you're paying a flat fee and transferring this 1TB won't cost you anything extra. I bet that Boeing is quite a bit more expensive.
Secondly, at some point the article assumes the 'transfer rate' of the Boeing to be 222Mbps. While this might be true for this practical example--let's ignore that you actually need to get the data on the plane in the first place--I bet that you could load it up from bottom to top and reach practically a speed of many gigabits ifnot terabits per second.
Thirdly, the Boeing flies with physical stuff. If the plane crashes, the data is lost. You would need backups, which take time. Over the internet it's not even possible to transfer the original medium; you'd need to first transfer and then delete it.
Fourthly, while it might be true that a packet gets corrupted 28 times during this 1TB transfer (I myself do not have statistics on this, but let's assume), on the internet you can retransmit a packet. Try retransmitting that one sector on the harddrive in under a second.
Fifthly, the article goes on about how TCP needs to wait for an acknowledgement (or 'ack' in short). I've made this mistake before when choosing for UDP instead of TCP because "it would not have to wait for acks and thus make my game much faster". It's wrong because there is a so-called congestion window. I do not know the exact figures, but it's like this: The server sends packet one. Packet one is in transit. The server sends packet two. Packet one and two are in transit. The server sends packet three. Packet one arrives. Packet two and three are in transit. The server sends packet four; the client sends ack 1. Packet 2, 3, 4 and ack 1 are in transit. Etc. The thing is that the server can send up to X packets ahead, without receiving an ack.
Sixthly, the article finally concludes that this is why you should choose for Cloudflare--so it was an advertisement after all. That explains why it's told in this story-like way and why it contains so many technical errors.
- deleted 14y ago[deleted]
- jgrahamc 14y agoTo address some of your points: 1. Yes, physical shipping is more practical than using the Internet for large transfers and this is done frequently. For example, Amazon Web Services offers the possibility to send them disks: http://aws.amazon.com/importexport/ http://aws.amazon.com/importexport/ Shipping of disks is also common in the movie industry. For example, a lot of digital movie distribution to cinemas relies on shipping of hard drives. 2. I used a statistic of 0.1% packet loss on the Internet and 28,000 flights per day to arrive at 28 flights lost per day. 3. There are two interacting things happening in TCP: the congestion window (which limits the number of outstanding _packets_) and the receive window which limits the number of outstanding bytes. This blog post does not address the congestion window at all and I assume that the receive window can always be filled. Thus is _overestimates_ what might be possible on a real link. 4. For very large transfers there are improvements that can be made using UDP and there are protocols that do just that. See, for example, TixelTec.
- masklinn 14y ago> Shipping of disks is also common in the movie industry. As well as sciences based on massive amounts of data (astrophysics and particle physics for instance, where experimental systems can produce terabytes per day), financial data analytics, or petroleum seismic surveys.
- tedunangst 14y agoAmazon allows you to send them hard drives if you have lots of data, so yes, it's more practical. You should calculate how large a window you need to fill a 100mbps pipe between SF and London. Then calculate how likely it is to remain there before you drop a packet, and how long it takes to detect a dropped packet with typical timeouts, and so on.