Skip to main content

Buffer Requirements for High-Speed Routers

Nice article by Damon Wischik


1. Introduction
Today, the buffer size in core Internet routers is
typically chosen according to a rule of thumb which
says: provide at least one round trip time's worth of
buffering. The round trip time is often taken to be
around 250ms (it takes 134ms to send a packet half
way round the world and back, but queueing delay
may plausibly add 100ms). A 40Gb/s linecard
therefore needs 1.25GByte of memory.
Such large memories are hard to build in electronics.
(The problem is that data can arrive at line rate, so
the memory needs to be writeable at line rate. Such a
high memory bandwidth is hard to engineer—and
DRAM access speeds increases at only 7.5% a year
[6].) Such large memories are also wildly impractical
for any all-optical router that we can conceive of
today.
Recent theoretical work has challenged the rule of
thumb: it seems that a buffer of just 20 packets
should be sufficient. The modeling behind this deals
with TCP's algorithm for congestion control, with very
short-timescale traffic statistics, and with queueing
theory for Poisson traffic. (Long-range dependence
has no bearing on buffer size.) This article outlines
the theory.
Practical work has also challenged the rule of thumb.
A measurement study of a Sprint backbone router [1]
found that the queue size hardly ever exceeded 10
packets! (perhaps not surprising given that Sprint
aims to keep utilization below 20%). Preliminary
experiments on working routers [15] suggest that
buffers can be much smaller than they are now,
though the experimentation does not yet make clear
quite how much.
Small buffers have obvious practical benefits. In an
electronic router, the buffer could be on-chip, giving
much higher memory bandwidth. In an all-optical
router, 20-packet buffers might become feasible in the
coming few years.


more on the link


Popular posts from this blog

IOS on Unix (IOU)

source http://evilrouters.net/2011/01/18/cisco-iou-faq/ What is IOU? From the Cisco Engineering Education web site (a long time ago): IOS on Unix (IOU) is a fully working version of IOS that runs as a user mode UNIX (Solaris) process. IOU is built as a native Solaris image and run just like any other program. IOU supports all platform independent protocols and features. What operating systems does IOU run on? It is my understanding that, initially, IOU was Solaris (SPARC) only. Nowadays, however, there are also builds for OS X and Linux. Similar to dynamips, IOU allows you to build out a network topology on a computer, without the need for physical routers. This is useful for validating designs, proof-of-concept testing, and certification self-study. Is my system compatible with IOU? You will need to be running the operating system that your IOU image were built for, obviously. Other than that, there are no special requirements to run IOU. It is not very CPU- or memory-intensive, unlik...

Impressed with Poly brand for conference headphones

I previously used my Sony XM4 headphones for calls and initially found them versatile for multiple purposes. However, as my meetings extended to several hours, I noticed they became less comfortable. To address this, I upgraded to wireless headphones from Poly, which offer significantly improved comfort. While I don’t plan to use them for music listening, my initial impression is very positive.

Flapping LDP/RSVP on Olive

I had a strange problem where the LDP and RSVP was flapping on JunOS/Olive and I think I managed to fix it by changing the driver from e1000 to i82559er and lo0.0 with 127.0.0.1.  I don't want to spend more time investigating it but if someone have similar problem at least this comment could be a good start. root@jr2>  *** MPLS *** May 21 14:27:21.472443 Session 4.4.4.4 hold timer expired in Operational state May 21 14:27:21.473451 Connection 4.4.4.4 state Open -> Closed May 21 14:27:21.473838 Session 4.4.4.4 GR state Operational -> Nonexistent May 21 14:27:21.473923 Session 4.4.4.4 state Operational -> Closing May 21 14:27:21.474054 LDP session 4.4.4.4 is down, reason: hold time expired May 21 14:27:21.474364 RPD_LDP_SESSIONDOWN: LDP session 4.4.4.4 is down, reason: hold time expired May 21 14:27:21.475567 Session 4.4.4.4 state Closing -> Nonexistent May 21 14:27:21.476180 CHANGE   317024 /52          nhid ...