From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Jeremy Austin via Rpm <rpm@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
cake@lists.bufferbloat.net, l4s-discuss@ietf.org
Subject: Re: [Starlink] [L4s-discuss] Understanding Latency 2.0 - Free Webinar Series: December 11-13, 2023 @ 4PM CET | 10AM EST | 7AM PST
Date: Mon, 27 Nov 2023 09:17:58 -0800 [thread overview]
Message-ID: <7634485fb330acb0cf2f3c40ff863588@rjmcmahon.com> (raw)
In-Reply-To: <CAJUtOOhoU66vT97oXaNAwrjXYONDH67_htsbs3cGX5EB6ZSjiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
I'm a late edition as a speaker. I'll go over, very briefly,
o) Why latency engineers should use iperf 2 over iperf 3
o) Clock sync options for one way delay (OWD), GPS pps & PTP
o) Iperf 2 latency metrics
o) Little's Law and bufferbloat displacement units in memory (packets,
bytes)
o) WiFi low latency table
o) Sense of urgency reminder - low latency networks aren't just needed
for high frequency traders
Also, I'll be presenting a similar presentation for the FCC TAC soon.
Let me know if any of your engineering teams need a longer presentation,
e.g. WiFi latency technologies, tools, and metrics. Or how to build WiFi
test rigs with variable channel conditions and statistical process
controls. Or why iperf 2 is preferred and how a united group behind
iperf 2 could help move things along.
Bob
> Hello to all,
>
> Register here: https://www.understandinglatency.com
>
> In the mean time, you can watch 1.0 here:
> https://www.understandinglatency.com/understanding-latency-2023
>
> See you all in December!
>
> All the best,
>
> Frank
>
> Frantisek (Frank) Borsik
>
> https://www.linkedin.com/in/frantisekborsik
>
> Signal, Telegram, WhatsApp: +421919416714
>
> iMessage, mobile: +420775230885
>
> Skype: casioa5302ca
>
> frantisek.borsik@gmail.com
[-- Attachment #2: WiFiLowLatencyTech.png --]
[-- Type: image/png, Size: 185215 bytes --]
prev parent reply other threads:[~2023-11-27 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 13:30 [Starlink] " Frantisek Borsik
2023-11-27 17:17 ` rjmcmahon [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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7634485fb330acb0cf2f3c40ff863588@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=frantisek.borsik@gmail.com \
--cc=l4s-discuss@ietf.org \
--cc=libreqos@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.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