--- Begin Message ---
I think we need the language of math here. It seems like the network power
metric, introduced by Kleinrock and Jaffe in the late 70s, is something
useful. Effective end/end queue depths per Little's law also seems useful.
Both are available in iperf 2 from a test perspective.
> On 2 Jul, 2021, at 7:59 pm, Stephen Hemminger
> wrote:
>
> In real world tests, TCP Cubic will consume any buffer it sees at a
> congested link. Maybe that is what they mean by capture effect.
First, I'll note that what they call "small buffer" corresponds to about a
tenth of a millisecond
--- Begin Message ---
The argument is absolutely correct for Reno, CUBIC and all
other self-clocked protocols. One of the core assumptions in Jacobson88,
was that the clock for the entire system comes from packets draining
through the bottleneck queue. In this world, the clock is intrinsically
On Fri, 2 Jul 2021 09:42:24 -0700
Dave Taht wrote:
> "Debunking Bechtolsheim credibly would get a lot of attention to the
> bufferbloat cause, I suspect." - dpreed
>
> "Why Big Data Needs Big Buffer Switches" -
> http://www.arista.com/assets/data/pdf/Whitepapers/BigDataBigBuffers-WP.pdf
>
"Debunking Bechtolsheim credibly would get a lot of attention to the
bufferbloat cause, I suspect." - dpreed
"Why Big Data Needs Big Buffer Switches" -
http://www.arista.com/assets/data/pdf/Whitepapers/BigDataBigBuffers-WP.pdf
..
i think i've just gained access to a few networks with arista
