From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jason Iannone <jason.iannone@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
Simon Sundberg <simon.sundberg@kau.se>
Subject: Re: [Bloat] Trouble Installing PPing in MacOS
Date: Sat, 27 Feb 2021 17:49:41 +0100 [thread overview]
Message-ID: <87eeh1xxp6.fsf@toke.dk> (raw)
In-Reply-To: <CAGL1wDT_f3CXMzjGmkPvBebca_a9G=mUjhY2_OUoQ_XCaFKxaw@mail.gmail.com>
Jason Iannone <jason.iannone@gmail.com> writes:
> Ideally, always on monitoring and export at the PE. An incremental first
> step in an adhoc off box tester, maybe deployed with the perfsonar suite.
Right. Are any of those boxes Linux-based? Otherwise the BPF
implementation is not much use to you :)
> Meaningfully visualizing the output seems challenging. Do you have any
> insights on that part?
No concrete plans yet, but the obvious thing that comes to mind is
looking for latency variation within flows, possibly correlating it with
rate. I tried to do something with the Measurement Labs NDT dataset some
years back:
https://dl.acm.org/doi/10.1145/2999572.2999603
For a middlebox monitor, the most interesting for identifying possible
interventions is to figure out which path the data corresponds to.
Depends a little on the network topology and the position of the
middlebox what would be a good way to do that...
-Toke
next prev parent reply other threads:[~2021-02-27 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 15:58 Jason Iannone
2021-02-25 16:52 ` Toke Høiland-Jørgensen
2021-02-25 18:02 ` Jason Iannone
2021-02-26 12:56 ` Jason Iannone
2021-02-26 21:06 ` Toke Høiland-Jørgensen
2021-02-27 0:36 ` Jason Iannone
2021-02-27 2:22 ` [Bloat] offtopic to: " David Collier-Brown
2021-02-27 16:00 ` [Bloat] " Toke Høiland-Jørgensen
2021-02-27 16:31 ` Jason Iannone
2021-02-27 16:49 ` Toke Høiland-Jørgensen [this message]
2021-02-26 22:16 ` Kathleen Nichols
2021-02-27 1:36 ` Jason Iannone
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=87eeh1xxp6.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=jason.iannone@gmail.com \
--cc=simon.sundberg@kau.se \
/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