FAST TCP

From Wikipedia, the free encyclopedia
Jump to: navigation, search

FAST TCP (also written FastTCP) is a TCP congestion avoidance algorithm especially targeted at long-distance, high latency links, developed at the Netlab, California Institute of Technology and now being commercialized by FastSoft. FastSoft was acquired by Akamai Technologies in 2012.[1]

FastTCP is compatible with existing TCP algorithms, requiring modification only to the computer which is sending data.

Name[edit]

The name FAST is a recursive acronym for FAST AQM Scalable TCP, where AQM stands for Active Queue Management, and TCP stands for Transmission Control Protocol.

Principles of operation[edit]

The role of congestion control is to moderate the rate at which data is transmitted, according to the capacity of the network and the rate at which other users are transmitting. Like TCP Vegas, FAST TCP[2] [3] uses queueing delay instead of loss probability as a congestion signal.

Most current congestion control algorithms detect congestion and slow down when they discover that packets are being dropped, so that the average sending rate depends on the loss probability. This has two drawbacks. First, low loss probabilities are required to sustain high data rates; in the case of TCP Reno, very low loss probabilities are required, but even new congestion avoidance algorithms such as H-TCP, BIC TCP and HSTCP require loss rates lower than those provided by most wireless wide area networks. Moreover, packet loss only provides a single bit of information about the congestion level, whereas delay is a continuous quantity and in principle provides more information about the network.

A FAST TCP flow seeks to maintain a constant number of packets in queues throughout the network. The number of packets in queues is estimated by measuring the difference between the observed round trip time (RTT) and the base RTT, defined as the round trip time when there is no queueing. The base RTT is estimated as the minimum observed RTT for the connection. If too few packets are queued, the sending rate is increased, while if too many are queued, the rate is decreased. In this respect, it is a direct descendant of TCP Vegas.

The difference between TCP Vegas and FAST TCP lies in the way in which the rate is adjusted when the number of packets stored is too small or large. TCP Vegas makes fixed size adjustments to the rate, independent of how far the current rate is from the target rate. FAST TCP makes larger steps when the system is further from equilibrium and smaller steps near equilibrium. This improves the speed of convergence and the stability.

Strengths and weaknesses[edit]

Delay-based algorithms can, in principle, maintain a constant window size, avoiding the oscillations inherent in loss-based algorithms. However, they also detect congestion earlier than loss-based algorithms, since delay corresponds to partially filled buffers, while loss results from totally filled buffers. This can be either a strength or a weakness. If the only protocol used in a network is delay-based, then the inefficiency of loss can be avoided; however, if loss-based and delay-based protocols share the network,[4] then delay-based algorithms tend to be less aggressive. This can be overcome by suitable choice of parameters, leading to complex interactions studied by Tang et al.

Delay measurements are also subject to jitter as a result of operating system scheduling, or bus contention.

Whether the strengths or weaknesses prevail is not clear, and depends in large part on the particular scenario.

Intellectual property[edit]

Unlike most TCP congestion avoidance algorithms, FAST TCP is protected by several patents.[5][6] Instead of seeking standardization by the IETF, the inventors of FAST, notably Steven Low and Cheng Jin, are seeking to commercialize it through the company FastSoft. Currently FastSoft sells a 1-Unit rack appliance which can be deployed at the sender-side with no other software or hardware modifications needed on either end.

See also[edit]

References[edit]

  1. ^ Young, Jeff (2012-09-13). "Akamai Acquires FastSoft". PR Newswire. Retrieved 2012-09-13. 
  2. ^ Nick, Barone; Jin, Cheng; Low, Steven H. and Hegde, Sanjay (2006). "FAST TCP: motivation, architecture, algorithms, performance". IEEE/ACM Trans. on Networking 14 (6): 1246–1259. doi:10.1109/TNET.2006.886335. 
  3. ^ Jin, Cheng; Wei, David X.; Low, Steven H.; Buhrmaster, G.; Bunn, J.; Choe, D. H.; Cottrell, R. L. A.; Doyle, J. C.; Feng, W.; Martin, O.; Newman, H. Paganini, F.; Ravot, S.; Singh, S. (2005). "FAST TCP: from theory to experiments". IEEE Network 19 (1): 4–11. doi:10.1109/MNET.2005.1383434. 
  4. ^ Tang, Ao; Wang, Jiantao; Low, Steven H. and Chiang, Mung (March 2005). Network Equilibrium of heterogeneous congestion control protocols. IEEE INFOCOM. Miami, FL. 
  5. ^ Jin, Cheng; Low, Steven H.; Wei, Xiaoliang (2005-01-27). "Method and apparatus for network congestion control". United States Patent & Trademark Office. Retrieved 2006-11-05. 
  6. ^ Jin, Cheng; Low, Steven H.; Wei, David X.; Wydrowski, Bartek; Tang, Ao; Choe, Hyojeong (2006-03-09). "Method and apparatus for network congestion control using queue control and one-way delay measurements". United States Patent & Trademark Office. Retrieved 2006-11-05. 

External links[edit]