81–90 of 172 posts
Earlier quoted context omitted.
There is quite a bit of documentation on this particular snake oil: https://patents.justia.com/patent/20090063698 https://en.wikipedia.org/wiki/Fast_and_Secure_Protocol
What is it about it that makes it snake oil?
Earlier quoted context omitted.
The author is discussing intercontinental data transfers. Not many organizations have a WAN that can cross oceans without hitting the internet.
almost all HE and research institutions participate in nrens which provide 3xacrly those peerings
Earlier quoted context omitted.
>"Another advantage, until recently, was out-of-order delivery." Can you elaborate on this? Which recent development are you referring to? Thanks.
Doesn't TCP have an ability to re-send dropped packets, now, without sending everything after them? I thought they called it selective re-send, or selective ack, or something. Maybe the receiver could send an ACK with a bitmap of which packets it got, and the sender would fill in the holes?
I've seen rather good speeds over some bad links from my bittorrent server using large window sizes (up to 9), BBR flow control, ECN fully enabled, and SACK.
Earlier quoted context omitted.
You can compress your data beforehand using zip or another tool. Eg. Tools like https://en.wikipedia.org/wiki/Compression_of_Genomic_Sequenc...
Zip is now effectively obsolete. Good ones lately are Zstd and Lz4, depending on your needs. Lz4 doesn't compress as much, but it is very, very fast. Zstd compresses better than Zip, and unpacks many times faster. It can re-use a custom dictionary saved off from a previous compression, so you can get quick startup time for later fragments.
Try looking at bbcp perhaps? http://pcbunn.cithep.caltech.edu/bbcp/using_bbcp.htm
Also, this senior dev never wrote unit tests.
On the other hand, maybe bbcp will work, and the senior dev just didn't know what he was doing. There was another senior dev who, seeing what was coming down the pike, left his job, and on his way out he was like, "yeah you can do it with bbcp, just you gotta tweak your tcp congestion rules on all the hops (which we could do, but is probably not an option for OP)"
Earlier quoted context omitted.
Are you familiar with UDT ( http://udt.sourceforge.net/ ) ? How does it compare to Aspera ? Thanks!
I was not familiar with it. It looks like you could build a good-enough file transfer system on top of UDT, but probably not with the rate control protocols they provide. One problem with UDP protocols over the open internet is that you cannot trust UDP packet contents, which could come from anywhere.