From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] congestion control and video conferencing
Date: Tue, 3 Dec 2013 13:22:30 -0800 [thread overview]
Message-ID: <CAA93jw4tWKbWvFKY1dDkX+pRfoM+EbrW_Ohqn4zB2KxiDFX6GA@mail.gmail.com> (raw)
re: http://conferences.sigcomm.org/sigcomm/2013/papers/fhmn/p21.pdf
"We have found that the algorithm works as expected when a GCC ow
accesses the bottleneck in isolation, whereas it is not able to
provide a fair band-
width utilization when a GCC flow shares the bottleneck with either a
GCC or a TCP flow."
I basically long ago came to the conclusion that video conferencing
can't work without aqm and packet scheduling on the bottleneck links.
Period. I wasn't aware there was also trouble even with two video
conferencing flows sharing the same link!
I run webrtc based and google hangout based talks through cerowrt with
fq_codel all the time while doing other benchmarks, but haven't come
up with good ways to quantify that. The results are generally pretty
spectacular with the few glitches I get attributable to wifi
misbehavior more than anything else.
Is anybody else testing webrtc through various aqm technologies?
I'd like to repeat this paper in a fq_codeled/pied/red'd environment
and see what happens... anyone interested in helping?
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2013-12-03 21:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw4tWKbWvFKY1dDkX+pRfoM+EbrW_Ohqn4zB2KxiDFX6GA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@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