Yeah. I admit to muddying the waters because I think of the size of a buffer as being in megabytes and the size of a queue (latency) as being in milliseconds. I think the tests attempt to measure the worst possible latency/queue that can occur on a path.
On 8/27/16 4:46 AM, Rich Brown wrote: > It has always been my intent to define bufferbloat as *latency*. The > first sentence on www.bufferbloat.net says, "Bufferbloat is the > undesirable latency that comes from a router or other network > equipment buffering too much data." > > That definition focuses on observable/measurable values. It sidesteps > objections I've seen on the forums, "How could $TEST measure the size > of buffers?" > > So what matters is whether the buffers (of any size) are filling up. > _______________________________________________ Bloat mailing list > [email protected] > https://lists.bufferbloat.net/listinfo/bloat > _______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
