On Tue, Feb 25, 2014 at 11:02 AM, Nicholas Weaver <nweaver@icsi.berkeley.edu> wrote:

On Feb 25, 2014, at 7:59 AM, Jim Gettys <jg@freedesktop.org> wrote:
> So it is arguably a "bug" in netalyzr.  It is certainly extremely misleading.
>
> Nick?

Rewriting it as a TCP-based stresser is definatly on our to-do list.

Good; though I'm not sure you'll be able to build a TCP one that fills the buffers fast enough to determine some of the buffering out there (at least without hacking the TCP implementation, anyway).

The other piece of this is detecting flow queuing being active; this makes a bigger difference to actual latency than mark/drop algorithms do by themselves.
                                  - Jim


--
Nicholas Weaver                  it is a tale, told by an idiot,
nweaver@icsi.berkeley.edu                full of sound and fury,
510-666-2903                                 .signifying nothing
PGP: http://www1.icsi.berkeley.edu/~nweaver/data/nweaver_pub.asc