• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

DMCA

Sizing Router Buffers (2004)

Cached

  • Download as a PDF

Download Links

  • [www.sigcomm.org]
  • [www.acm.org]
  • [acm.org]
  • [www.cs.cornell.edu]
  • [conferences.sigcomm.org]
  • [klamath.stanford.edu]
  • [klamath.stanford.edu]
  • [klamath.stanford.edu]
  • [klamath.stanford.edu]
  • [www-rcf.usc.edu]
  • [tiny-tera.stanford.edu]
  • [yuba.stanford.edu]
  • [www.eecs.berkeley.edu]
  • [cs.northwestern.edu]
  • [www.cse.iitb.ac.in]
  • [www.cse.iitb.ac.in]
  • [www.cse.iitb.ac.in]
  • [sharif.edu]
  • [cs.northwestern.edu]
  • [www.eecs.berkeley.edu]
  • [web.univ-pau.fr]
  • [yuba.stanford.edu]
  • [comnet.technion.ac.il]
  • [www.ee.technion.ac.il]
  • [www-comnet.technion.ac.il]
  • [tiny-tera.stanford.edu]
  • [tiny-tera.stanford.edu]
  • [tiny-tera.stanford.edu]
  • [klamath.stanford.edu]
  • [yuba.stanford.edu]
  • [yuba.stanford.edu]
  • [yuba.stanford.edu]
  • [yuba.stanford.edu]
  • [comnet.technion.ac.il]
  • [www.ee.technion.ac.il]
  • [www-comnet.technion.ac.il]

  • Other Repositories/Bibliography

  • DBLP
  • Save to List
  • Add to Collection
  • Correct Errors
  • Monitor Changes
by Guido Appenzeller, Isaac Keslassy, Nick McKeown
Citations:352 - 17 self
  • Summary
  • Citations
  • Active Bibliography
  • Co-citation
  • Clustered Documents
  • Version History

BibTeX

@MISC{Appenzeller04sizingrouter,
    author = {Guido Appenzeller and Isaac Keslassy and Nick McKeown},
    title = {Sizing Router Buffers},
    year = {2004}
}

Share

Facebook Twitter Reddit Bibsonomy

OpenURL

 

Abstract

All Internet routers contain buffers to hold packets during times of congestion. Today, the size of the buffers is determined by the dynamics of TCP’s congestion control algorithm. In particular, the goal is to make sure that when a link is congested, it is busy 100 % of the time; which is equivalent to making sure its buffer never goes empty. A widely used rule-of-thumb states that each link needs a buffer of size B = RT T × C, where RT T is the average round-trip time of a flow passing across the link, and C is the data rate of the link. For example, a 10Gb/s router linecard needs approximately 250ms × 10Gb/s = 2.5Gbits of buffers; and the amount of buffering grows linearly with the line-rate. Such large buffers are challenging for router manufacturers, who must use large, slow, off-chip DRAMs. And queueing delays can be long, have high variance, and may destabilize the congestion control algorithms. In this paper we argue that the rule-of-thumb (B = RT T ×C) is now outdated and incorrect for backbone routers. This is because of the large number of flows (TCP connections) multiplexed together on a single backbone link. Using theory, simulation and experiments on a network of real routers, we show that a link with n flows requires no more than B = (RT T × C) / √ n, for long-lived or short-lived TCP flows. The consequences on router design are enormous: A 2.5Gb/s link carrying 10,000 flows could reduce its buffers by 99 % with negligible difference in throughput; and a 10Gb/s link carrying 50,000 flows requires only 10Mbits of buffering, which can easily be implemented using fast, on-chip SRAM.

Keyphrases

router buffer    router linecard    large buffer    real router    internet router    large number    on-chip sram    backbone router    congestion control algorithm    tcp congestion control algorithm    router manufacturer    single backbone link    average round-trip time    high variance    off-chip dram    flow passing    size rt    rule-of-thumb state    router design    negligible difference    short-lived tcp    data rate    tcp connection   

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University