Re: [Bloat] delay-under-load really helps diagnose real world problems

[jb <justin@dslr.net>]

[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]

I have made the following changes a few hours ago:

Bloat latency stats run on every connection now except GPRS and 3G
if you don't seem them during the test (mobile), they should be there
afterwards.

Download phase waits for quiescent latency measurements, defined by
less than 2x the lowest ping seen, or it simply gives up waiting and
continues.

The flow stats table has combined stats per server, so the megabit per
stream are
summed and the other measurements are averaged. I'm not entirely trusting
of the RTT and RTT Variance numbers from Linux, they come from the TCP_INFO
structure but are probably heavily biased to the end of the connection
rather
than the entire connection. However the re-transmits are definitely ok and
the
congestion window packet count looks about right too.

that's it..


On Sat, Apr 25, 2015 at 12:58 AM, Matthew Ford <ford@isoc.org> wrote:

>
> > On 23 Apr 2015, at 22:55, Bill Ver Steeg (versteb) <versteb@cisco.com>
> wrote:
> >
> > So, hats off to Justin!
>
> A big +1 to what Bill said from me. This tool is great and has already
> helped me improve my own home network setup.
>
> A colleague noted that selecting ‘Public WiFi’ as connection type results
> in no bloat measurements. Which connection types are bloat measurements
> enabled for? What’s the plan for the others?
>
> Mat
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 2247 bytes --]