|This article needs additional citations for verification. (January 2016) (Learn how and when to remove this template message)|
It is a less aggressive and more systematic derivative of BIC TCP, in which the window size is a cubic function of time since the last congestion event, with the inflection point set to the window size prior to the event. Because it is a cubic function, there are two components to window growth. The first is a concave portion where the window size quickly ramps up to the size before the last congestion event. Next is the convex growth where CUBIC probes for more bandwidth, slowly at first then very rapidly. CUBIC spends a lot of time at a plateau between the concave and convex growth region which allows the network to stabilize before CUBIC begins looking for more bandwidth.
Another major difference between CUBIC and standard TCP flavors is that it does not rely on the receipt of ACKs to increase the window size. CUBIC's window size is dependent only on the last congestion event. With standard TCP, flows with very short RTTs will receive ACKs faster and therefore have their congestion windows grow faster than other flows with longer RTTs. CUBIC allows for more fairness between flows since the window growth is independent of RTT.
CUBIC TCP is implemented and used by default in Linux kernels 2.6.19 and above.
-  S. Ha, I. Rhee, & L. Xu, "CUBIC: A New TCP-Friendly High-Speed TCP Variant", PDF copy of journal article
|This computer networking article is a stub. You can help Wikipedia by expanding it.|