From: cloneman <bufferbloat@flamingpc.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Does VDSL interleaving+FEC help bufferbloat?
Date: Thu, 3 Jan 2019 16:38:12 -0500 [thread overview]
Message-ID: <CABQZMoLhpvaFcDbZeWgpmjzPRCYCMrOtjAzM_Q7+9W6_N8h6cA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
Interleaving on DSL is enabled by many providers which allegedly provides
some packet loss protection at the cost of some latency.
I think it's designed mainly Layer 1 line noise, but now I'm wondering if
it might also translate to other benefits, even on a clean DSL line that
doesn't *need* interleave.
Question:
Is interleaving protective of packet loss due to momentary spikes on the
downloads?
I tested it a bit with the help of my ISP
VDSL:
Interleave+FEC On (15ms first hop) 3% packet loss on steam download stress
Interleave+FEC OFF (4ms first hop) 5-6% packet loss on steam download
stress
With fq_codel: (-15% bw)
Both had 0.3% packet loss (very good) on steam Download stress
Of note, steam downloads used to break fq_codel for me (20 flows split
evenly is how they designed it *sigh*) but it appears that it's working
well now, perhaps steam *finally* fixed their stuff. Steam stress is
performed by downloading any of their free games with their client software
e.g. Dota2.
tl-dr; interesting to test weather interleave+FEC, a technology designed
for layer 1 noise, can help with layer 3 ingress contention for resources.
Also, I found a guy who designed a layer 3 FEC protocol designed for
terrible connections: https://github.com/wangyu-/tinyfecVPN
If anyone wants to comment on that, I think it's nice to know that it
exists.
[-- Attachment #2: Type: text/html, Size: 2226 bytes --]
next reply other threads:[~2019-01-03 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 21:38 cloneman [this message]
2019-01-04 4:01 ` Jonathan Morton
2019-01-04 13:21 ` Simon Barber
2019-01-04 17:10 ` Dave Taht
2019-01-04 17:43 ` Mikael Abrahamsson
2019-01-04 17:52 ` Jan Ceuleers
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=CABQZMoLhpvaFcDbZeWgpmjzPRCYCMrOtjAzM_Q7+9W6_N8h6cA@mail.gmail.com \
--to=bufferbloat@flamingpc.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