From: Dave Taht <dave.taht@gmail.com>
To: Jan Ceuleers <jan.ceuleers@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Speed tests - attribution of latency to relevant network hops
Date: Thu, 30 Jul 2015 17:27:12 +0200 [thread overview]
Message-ID: <CAA93jw7xVcDd0Rw6Hj94A0S9GsYDmechSNxfKmQeTC6DEvLiHA@mail.gmail.com> (raw)
In-Reply-To: <55BA3ABD.2010902@gmail.com>
The tool for looking at this is called "mtr", which is available in
various forms for linux, osx, and windows.
It was originally part of the rrul spec, but parsing it's output is a
little difficult (or was - there is csv support for it now in linux
mainline), and the biggest reason left (besides lack of time to
implement it - patches gladly accepted!) we don't use it yet is that
it imparts enough traffic to measurably jigger the other results at
lower bandwidths.
Certainly, instead of blending together the outputs of multiple
separate tools as we currently do with flent, it would be better to
have one specific tool that measured everything we care about all at
the same time and (for example) saw, rather than estimated, acks - but
that requires a scale of development effort and funding that we have
never had.
I do have hope that one day webrtc could be leveraged to give us udp
measurements from within a browser. The current dslreports ping over
tcp method is subject to a multiplicity of problems. I would not mind
at all if browsers gained the ability to set the ttl, also.
prev parent reply other threads:[~2015-07-30 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 19:39 Jan Ceuleers
2015-07-29 21:28 ` David Lang
2015-07-30 4:52 ` Mikael Abrahamsson
2015-07-30 5:17 ` Jan Ceuleers
2015-07-30 13:04 ` Bill Ver Steeg (versteb)
2015-07-30 14:54 ` Jan Ceuleers
2015-07-30 15:27 ` Dave Taht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7xVcDd0Rw6Hj94A0S9GsYDmechSNxfKmQeTC6DEvLiHA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jan.ceuleers@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox