From: "Rodney W. Grimes" <starlink@gndrsh.dnsmgr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
BBR Development <bbr-dev@googlegroups.com>,
Rpm <rpm@lists.bufferbloat.net>,
sander@comsys.rwth-aachen.de, grote@comsys.rwth-aachen.de,
wehrle@comsys.rwth-aachen.de, kunze@comsys.rwth-aachen.de
Subject: Re: [Starlink] Instant Messaging Meets Video Conferencing: Studying the Performance of IM Video Calls
Date: Fri, 30 Jun 2023 22:23:18 -0700 (PDT) [thread overview]
Message-ID: <202307010523.3615NILa077063@gndrsh.dnsmgr.net> (raw)
In-Reply-To: <CAA93jw5mYRytJSxAkjR8q4rq-ySDuzTiV7i+ee=ADt4oFnXrFQ@mail.gmail.com>
> This paper does a really good job of measuring the impacts of tcp
> cross traffic, including BBRv2, against the videoconferencing
> subsystems in signal, telegram, and whatsapp.
Did I miss something? The paper only shows a dumb bell topology with
instream traffic, I did not see any cross flow traffic testing.
>
> https://tma.ifip.org/2023/wp-content/uploads/sites/12/2023/06/tma2023-final37.pdf
>
> Naturally fq_codel shines. The paper also introduces a new means of
> measuring videoconferenceQoE, called BRISQUE.
>
> About my only kvetch is they didn't try cake, which has a different
> shaper, drops less packets, has less collisions, as well as diffserv
> support.
>
> Seeing BBRv2 stats and impact was very interesting also.
>
>
>
>
> --
> Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave T?ht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>
next prev parent reply other threads:[~2023-07-01 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 15:46 Dave Taht
2023-07-01 5:23 ` Rodney W. Grimes [this message]
2023-07-01 15:30 ` Dave Taht
2023-07-02 6:27 ` Rodney W. Grimes
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=202307010523.3615NILa077063@gndrsh.dnsmgr.net \
--to=starlink@gndrsh.dnsmgr.net \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=grote@comsys.rwth-aachen.de \
--cc=kunze@comsys.rwth-aachen.de \
--cc=rpm@lists.bufferbloat.net \
--cc=sander@comsys.rwth-aachen.de \
--cc=starlink@lists.bufferbloat.net \
--cc=wehrle@comsys.rwth-aachen.de \
/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