From: "Rodney W. Grimes" <starlink@gndrsh.dnsmgr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Rodney W. Grimes" <starlink@gndrsh.dnsmgr.net>,
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: Sat, 1 Jul 2023 23:27:47 -0700 (PDT) [thread overview]
Message-ID: <202307020627.3626RlvU081450@gndrsh.dnsmgr.net> (raw)
In-Reply-To: <CAA93jw65W3hwp7OAQFPnEgkWeE4PX-smMM4w7itPUOy9S8sP9g@mail.gmail.com>
> On Sat, Jul 1, 2023 at 12:23?AM Rodney W. Grimes
> <starlink@gndrsh.dnsmgr.net> wrote:
> >
> > > 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.
>
> Do we share the same definition of cross traffic? The testbed consists
> of fifo, codel, and fq_codel queues, against 1-2 tcp flows, against a
> p2p videoconferencing flow.
What they did was measure competing flows on a COMMON PATH.
Using a COMMON path, that is not cross flow, at least by my understanding
of the definition of cross flow. The fact that they located
the competing flows ON THE SAME NODES it means only one flow or the
other flow can transmit a packet at a single instance in time, this
insuring that the transmission of packets is serialized by the node
between the competing flows.
>
> I am sometimes just as subject to confirmation bias as the next guy,
> and in re-reading this this morning I would have liked it if they had
> cited rfc8290, and extended their tests to use a bigger BDP for the
> fifo as well as tested web PLT. a shorter RTT would also be
> interesting in the case of a ptp app such as this.
>
> An exciting part to me remains in exploring the videoconferencing QoE
> technique they discuss (Brisque) which I haven?t found sources for
> yet...
>
>
> >
> > >
> > > 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
> > >
> > >
>
>
>
> --
> Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave T?ht CSO, LibreQos
>
>
prev parent reply other threads:[~2023-07-02 7:28 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
2023-07-01 15:30 ` Dave Taht
2023-07-02 6:27 ` Rodney W. Grimes [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=202307020627.3626RlvU081450@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