Re:Reliable, fast UDP-based data transfer protocol that outp...
by josephruscio on Tuesday October 20, 2009 @11:20PM
(#893951)
TCP's slow-start and exponential backoff algorithms are absolute murder when your pipe has a large bandwidth-delay product. There are a whole slew of UDP-based implementations (and a couple TCP variants) targeted at large data transfers over such pipes.
The underlying problem is trying to achieve fairness not only between instances of the new protocol itself (which this implementation and many others claim), but also fairness with instances of the legacy TCP protocol (this protocol's claim seems to be a little weaker here).
Re:Reliable, fast UDP-based data transfer protocol that outp...
by josephruscio on Wednesday October 21, 2009 @01:22AM
(#894105)
Yep. FastTCP is a pretty elegant algorithm that happens to covered by all sorts of patents. Was a company behind it as well that seems to still be doing OK (FastSoft). Unfortunately won't be turning up in Linux et al due to those angles :-(.
Re:Reliable, fast UDP-based data transfer protocol that outp...
by huhtenberg on Wednesday October 21, 2009 @02:18AM
(#894141)
There is also TCP/Vegas, which is based on the same idea, as good as FastTCP for all practical intents and purposes, comes with Linux 2.6 and unencumbered by the patents.
Re:Reliable, fast UDP-based data transfer protocol that outp...
by dedalus on Wednesday October 21, 2009 @01:12PM
(#895088)
I played with this and its not faster than other TCP. In fact my implementation of NetBLT (http://www.faqs.org/rfcs/rfc998.html) blows this one out of water.
An enhanced TCP that we use internally stacked up as follows w.r.t Normal TCP and FastTCP (times are for retreival of a 180KB file)
it's substantially faster than TCP because it doesn't provide any guarantees (e.g. error checking); consequently it's more difficult to work with. this protocol builds on top of UDP to provide all of the nice guarantees that TCP does.
Re:Reliable, fast UDP-based data transfer protocol that outp...
by clistctrl on Tuesday October 20, 2009 @11:14PM
(#893940)
This is really cool, I had tried making something like this a few years ago when I was working in a lab. Mine worked, but I never really got the time to perfect it.
The underlying problem is trying to achieve fairness not only between instances of the new protocol itself (which this implementation and many others claim), but also fairness with instances of the legacy TCP protocol (this protocol's claim seems to be a little weaker here).
An enhanced TCP that we use internally stacked up as follows w.r.t Normal TCP and FastTCP (times are for retreival of a 180KB file)
RTT Normal TCP FastTCP InternalTCP 48 548 205 180
94 984 359 232
140 1546 593 334
188 1985 797 381
UDT,for different latencies clocked as follows
48 - 3.498s 94 - 3.262s 140 -3.640s 188- 3.987s
Hope that makes it clear
it's substantially faster than TCP because it doesn't provide any guarantees (e.g. error checking); consequently it's more difficult to work with. this protocol builds on top of UDP to provide all of the nice guarantees that TCP does.