PCC: Re-architecting congestion control for consistent high performance

Mo Dong, Qingxi Li, Doron Zarchy, P. Brighten Godfrey, Michael Schapira

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

248 Scopus citations

Abstract

TCP and its variants have suffered from surprisingly poor performance for decades. We argue the TCP family has little hope of achieving consistent high performance due to a fundamental architectural deficiency: hardwiring packet-level events to control responses. We propose Performance-oriented Congestion Control (PCC), a new congestion control architecture in which each sender continuously observes the connection between its actions and empirically experienced performance, enabling it to consistently adopt actions that result in high performance. We prove that PCC converges to a stable and fair equilibrium. Across many real-world and challenging environments, PCC shows consistent and often 10× performance improvement, with better fairness and stability than TCP. PCC requires no router hardware support or new packet format.

Original languageAmerican English
Title of host publicationProceedings of the 12th USENIX Symposium on Networked Systems Design and Implementation, NSDI 2015
PublisherUSENIX
Pages395-408
Number of pages14
ISBN (Electronic)9781931971218
StatePublished - 2015
Event12th USENIX Symposium on Networked Systems Design and Implementation, NSDI 2015 - Oakland, United States
Duration: 4 May 20156 May 2015

Publication series

NameProceedings of the 12th USENIX Symposium on Networked Systems Design and Implementation, NSDI 2015

Conference

Conference12th USENIX Symposium on Networked Systems Design and Implementation, NSDI 2015
Country/TerritoryUnited States
CityOakland
Period4/05/156/05/15

Bibliographical note

Publisher Copyright:
© 2015 by The USENIX Association. All Rights Reserved.

Fingerprint

Dive into the research topics of 'PCC: Re-architecting congestion control for consistent high performance'. Together they form a unique fingerprint.

Cite this