From: Jason Iannone <jason.iannone@gmail.com>
To: nichols@pollere.net
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Trouble Installing PPing in MacOS
Date: Fri, 26 Feb 2021 20:36:26 -0500 [thread overview]
Message-ID: <CAGL1wDQLzMJy8bos0SvME2Or3jXL2uv=eYvULyVMMZSVy9R+rw@mail.gmail.com> (raw)
In-Reply-To: <293de1cf-ae10-5e77-81ba-59599cc6ef86@pollere.net>
[-- Attachment #1: Type: text/plain, Size: 2449 bytes --]
I watched your presentation at ucla on youtube. I wasn't expecting the talk
you ended up giving, but I think your experience is familiar.
Poking at data in different ways is interesting and it can be hard to
separate the wheat from the chaff. What presentation methods matter? What
presentation methods drive useful action?
I'm not a data science guy. At my core, I am a plumber. New and interesting
ways of visualizing what lives in the pipes can help me target problem
areas, the same way you noted with the 7 second delay in the university
science network in your presentation.
I appreciate the scope of pping. It's small and intentional. Anyway, I dig
the intent and the size and I hope to see more of this kind of work.
Thanks for replying,
Jason
On Fri, Feb 26, 2021, 5:16 PM Kathleen Nichols <nichols@pollere.net> wrote:
> On 2/26/21 4:56 AM, Jason Iannone wrote:
> ...
> > passively monitor production flows to get a novel sense of end to end
> > performance per flow. I don't know of any other passive monitoring
> > technique, beyond a port mirror + a whole gang of systems, that can
> > provide this level of detail. Please enlighten me if I'm wrong. The only
> > other passive monitoring mechanisms I'm aware of are SNMP polling,
> > IPFIX/*Flow, and Streaming Telemetry Interface. None of those systems
> > provide end to end flow performance details. The standard in-band active
> > monitoring tools are good for determining node to node and full path
> > metrics, but this provides a more complete picture of end to end
> > performance beyond active y.1731/802.3ag/OAM probes. I'm a little
> > surprised that I'm only learning about it now.
> >
>
> So, I worked on something I call TSDE (Transport Segment Delay
> Estimator) that lets you get a (noisy) one-way estimate of delay
> variation. I did pping as sort of a side product and as a way to find
> the minimum round trip delay since TSDE just gives variation. This was
> done under a DOE SBIR and Pollere has a patent on it but I would
> consider sharing information if someone wanted to develop an open source
> tool. (I feel that my own implementation is kind of fragile as I was
> using it to try different ideas for getting a good estimate. And I
> haven't done anything with it for several years.)
>
> Kathie
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 3295 bytes --]
prev parent reply other threads:[~2021-02-27 1:36 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
2021-02-26 22:16 ` Kathleen Nichols
2021-02-27 1:36 ` Jason Iannone [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='CAGL1wDQLzMJy8bos0SvME2Or3jXL2uv=eYvULyVMMZSVy9R+rw@mail.gmail.com' \
--to=jason.iannone@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=nichols@pollere.net \
/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