Computing Atlas

How Computing Was Built
Sign In
Text size
100%
Theme
Algorithm

Leaky bucket

Network Algorithm

The leaky bucket is an algorithm built on the picture of a bucket with a constant leak. If water is poured in faster on average than it leaks out, or if more is poured in at once than the bucket can hold, the bucket overflows. Applied to network traffic, the same picture decides whether a sequence of packets or other discrete events stays within agreed limits on its average rate and its peak rate, so that it can be used in traffic policing, traffic shaping and the scheduling of data transmissions on packet-switched and telecommunications networks. Two versions appear in the literature. In the meter version the bucket is a counter that is raised as each packet arrives and lowered at a fixed rate, and it only checks conformance. In the queue version the bucket is a queue that holds packets and releases them at a fixed rate, which smooths the traffic. The meter version is the mirror image of the token bucket, and the generic cell rate algorithm used for Asynchronous Transfer Mode networks is a form of it. Jonathan S. Turner is credited with the original description.

Connections

Credited To

Source Leaky bucket (Wikipedia)

In Field

Source Leaky bucket (Wikipedia)

Invented

Source Leaky bucket (Wikipedia)
Sources
Leaky bucket (Wikipedia)
  • In Group: Traffic Shaping and Medium Access, Introduction
    It is used in packet-switched computer networks and telecommunications networks in both the traffic policing, traffic shaping and scheduling of data transmissions
  • In Field: Computer Networking, Introduction [in-field]
    It is used in packet-switched computer networks and telecommunications networks
  • Credited To: Jonathan S. Turner, Introduction
    Jonathan S. Turner is credited with the original description of the leaky bucket algorithm
  • Invented: Jonathan S. Turner, Introduction
    Jonathan S. Turner is credited with the original description of the leaky bucket algorithm
View the Source
Comments (0)
No comments yet. Be the first to share a thought.
Reader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.