{"id":268788,"date":"2016-08-01T04:04:23","date_gmt":"2016-08-01T11:04:23","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/research\/?post_type=msr-project&p=268788"},"modified":"2016-08-11T22:44:19","modified_gmt":"2016-08-12T05:44:19","slug":"fuso-fast-multi-path-transport-loss-recovery-scheme-data-centers-2","status":"publish","type":"msr-project","link":"https:\/\/www.microsoft.com\/en-us\/research\/project\/fuso-fast-multi-path-transport-loss-recovery-scheme-data-centers-2\/","title":{"rendered":"FUSO: A Fast Multi-path Transport Loss Recovery Scheme for Data Centers"},"content":{"rendered":"

Packet loss in data centers, caused by both congestion and failures, greatly hurts the performance of the transport layer, leading to a long tail of flow completion time. FUSO is a fast multi-path transport loss recovery scheme for data centers, to help maintaining a consistent low flow completion time when facing packet losses. FUSO leverages the multi-path diversity in data centers to accelerate the loss recovery, attempting to be both “fast” and “cautious”. Specifically, when\u00a0a multi-path transport sender suspects loss on one sub-flow, recovery packets are immediately sent over another\u00a0sub-flow that is not or less lossy and<\/em> has spare congestion\u00a0window slots.\u00a0 FUSO is\u00a0fast in that it does not need to wait for timeout on the lossy sub-flow, and it is cautious in that it does not violate congestion control algorithm.<\/p>\n

Currently, FUSO is a kernel transport implementation which is built upon MPTCP\u2019s Linux implementation (v0.90). Our implementation is\u00a0publicly\u00a0available.<\/p>\n

Publication:<\/p>\n