Bandwidth Delay Product (BDP)

Understanding network capacity and optimization

What is Bandwidth Delay Product?

Definition: The Bandwidth Delay Product (BDP) is the maximum amount of data that can be "in flight" (transmitted but not yet acknowledged) on a network link at any given time. It represents the product of the link's bandwidth and its round-trip time (RTT).

BDP is a critical metric for optimizing network performance, particularly for TCP connections over high-bandwidth or high-latency networks.

BDP = Bandwidth × Round-Trip Time

Where:

  • Bandwidth = Data rate of the link (bits per second)
  • RTT = Round-trip time (seconds)
  • BDP = Result in bits (or bytes if bandwidth in bytes/sec)

Why BDP Matters

The BDP determines the optimal TCP window size needed to fully utilize available bandwidth:

Key Insight: If the TCP window size is smaller than the BDP, the sender will be idle waiting for acknowledgments, resulting in underutilization of the available bandwidth.

The "Pipe" Analogy

Think of a network link as a pipe:

  • Bandwidth = Diameter of the pipe (how much can flow)
  • Delay (RTT) = Length of the pipe (how long it takes)
  • BDP = Volume of the pipe (total capacity)

To keep the pipe full and maximize throughput, you need to send enough data to fill the entire pipe before waiting for acknowledgments.

Calculation Examples

Example 1: Local Network (LAN)

Given:

  • Bandwidth: 1 Gbps = 1,000,000,000 bps
  • RTT: 1 ms = 0.001 seconds

Calculation:

BDP = 1,000,000,000 × 0.001 = 1,000,000 bits = 125,000 bytes = 122 KB

TCP Window Size: At least 122 KB

Example 2: Satellite Link

Given:

  • Bandwidth: 10 Mbps = 10,000,000 bps
  • RTT: 600 ms = 0.6 seconds (geostationary satellite)

Calculation:

BDP = 10,000,000 × 0.6 = 6,000,000 bits = 750,000 bytes = 732 KB

TCP Window Size: At least 732 KB

Example 3: Transcontinental Link

Given:

  • Bandwidth: 100 Mbps = 100,000,000 bps
  • RTT: 150 ms = 0.15 seconds (US to Europe)

Calculation:

BDP = 100,000,000 × 0.15 = 15,000,000 bits = 1,875,000 bytes = 1.79 MB

TCP Window Size: At least 1.79 MB

Impact on TCP Performance

TCP Window Size

The TCP receive window advertises how much data the receiver can accept. For optimal performance:

TCP Window Size ≥ BDP
Scenario Window Size vs BDP Result
Optimal Window = BDP Full bandwidth utilization
Undersized Window < BDP Sender idles, throughput limited
Oversized Window > BDP No harm, extra buffering

TCP Window Scaling

Standard TCP window field is 16 bits, limiting window size to 65,535 bytes (64 KB). For high BDP networks:

  • RFC 1323: TCP Window Scaling option
  • Maximum window: 1 GB (with scale factor 14)
  • Enabled by default: Most modern operating systems

Factors Affecting BDP

1. Network Type

Network Type Typical RTT BDP Characteristics
LAN < 1 ms Low BDP, standard window OK
Metropolitan 5-20 ms Moderate BDP
Intercontinental 100-300 ms High BDP, needs tuning
Satellite 500-700 ms Very high BDP, critical tuning

2. Bandwidth Evolution

As bandwidth increases, BDP grows proportionally:

  • 1990s: 56 Kbps modems → Small BDP
  • 2000s: Broadband (1-10 Mbps) → Moderate BDP
  • 2010s: Fiber (100 Mbps - 1 Gbps) → Large BDP
  • 2020s: Multi-gigabit links → Very large BDP

Optimizing for High BDP Networks

1. Enable TCP Window Scaling

Linux:

sysctl -w net.ipv4.tcp_window_scaling=1

Windows: Enabled by default in Windows Vista+

2. Increase Buffer Sizes

Set TCP send/receive buffers to at least BDP:

net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216

3. Use TCP BBR Congestion Control

BBR (Bottleneck Bandwidth and RTT) algorithm better handles high BDP:

net.ipv4.tcp_congestion_control = bbr

4. Consider UDP-based Protocols

For very high BDP scenarios:

  • QUIC: Modern transport protocol (HTTP/3)
  • UDT: UDP-based Data Transfer
  • Custom protocols: Application-specific optimization

Real-World Applications

Data Centers

Low latency but very high bandwidth requires proper tuning to avoid bottlenecks in server-to-server communication.

Cloud Computing

Cross-region data transfer needs large TCP windows to maintain throughput over long distances.

Satellite Internet

Extremely high RTT (600ms+) requires massive TCP windows even at moderate bandwidth.

Content Delivery Networks (CDN)

Optimizing BDP for various client locations ensures fast content delivery globally.

Video Streaming

High-quality streaming requires sufficient buffering based on BDP to prevent interruptions.

Common Pitfalls

Problem Symptom Solution
Small TCP window Low throughput despite high bandwidth Enable window scaling, increase buffers
Disabled window scaling 64 KB throughput limit Enable TCP window scaling option
Packet loss Frequent retransmissions Investigate network quality, use better congestion control
Middlebox interference Window scaling stripped Check firewalls, NAT devices

Measuring BDP in Practice

Tools for Measurement

  • ping: Measure RTT
  • iperf3: Measure bandwidth and test TCP performance
  • traceroute: Identify network path and delays
  • netstat/ss: Monitor TCP window sizes
  • tcpdump/Wireshark: Analyze packet-level behavior

Key Takeaways

Remember:
  • BDP = Bandwidth × RTT (maximum data in flight)
  • TCP window size should be ≥ BDP for optimal performance
  • High bandwidth OR high latency = high BDP
  • Enable TCP window scaling for BDP > 64 KB
  • Satellite and long-distance links have very high BDP
  • Proper tuning critical for modern high-speed networks
  • Monitor and adjust based on actual network conditions