General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Pedro Tumusok <pedro.tumusok@gmail.com>
To: Jan Ceuleers <jan.ceuleers@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [aqm] the side effects of 330ms lag in the real world
Date: Wed, 30 Apr 2014 10:19:51 +0200	[thread overview]
Message-ID: <CACQiMXb4sG_VA=a-TGnKvnGrGfdXTebm2qoWVhYsw+dG=cNN+Q@mail.gmail.com> (raw)
In-Reply-To: <53609DFA.9040708@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]

On Wed, Apr 30, 2014 at 8:53 AM, Jan Ceuleers <jan.ceuleers@gmail.com>wrote:

> On 04/29/2014 07:01 PM, Toke Høiland-Jørgensen wrote:
> > However, as that graph shows, it is quite possible to completely avoid
> > bufferbloat by deploying the right shaping. And in that case fibre
> > *does* have a significant latency advantage. The best latency I've seen
> > to the upstream gateway on DSL has been ~12 ms.
>
> I am not an expert, but I believe that this is due to the use of
> interleaving. This is a method to improve the strength of forward error
> correction by spreading out the effects of impulse noise on DSL lines
> across multiple reed-solomon-protected codewords at the expense of latency.
>
> The topic is briefly discussed on the ADSL Wikipedia page.
>

Depending on the interleave depth you get extra latency. But there are also
different schemes you can use

Interleave, the one that basically came with ADSL.
Phyr, Broadcom evolution on interleave, that has less latency, I believe,
in most cases.
G.INP, which I have been told is a standardized version of Phyr.

All of these will affect the latency and by how much is also dependant on
the configuration you have done on your DSLAM. To add to the mess, not all
DSLAM's support phyr or g.inp and then up the complexity a bit with CPE
that supports one, two or all three of the technologies.

Ohh some ISPs might even not use interleave and just have the DSLAM setup
to do Fastmode/Fastpath or what the vendor decided to name the feature.

Pedro




> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>



-- 
Best regards / Mvh
Jan Pedro Tumusok

[-- Attachment #2: Type: text/html, Size: 2653 bytes --]

  reply	other threads:[~2014-04-30  8:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29  1:24 [Bloat] " Dave Taht
2014-04-29  7:08 ` [Bloat] [aqm] " Mikael Abrahamsson
2014-04-29  7:21   ` Fred Baker (fred)
2014-04-29  7:56     ` Mikael Abrahamsson
2014-04-29 15:46       ` Dave Taht
2014-04-29 16:51         ` Aaron Wood
2014-04-29 16:44       ` Jim Gettys
2014-04-29 16:57         ` Jim Gettys
2014-04-29 17:01         ` Toke Høiland-Jørgensen
2014-04-29 17:07           ` Jim Gettys
2014-04-29 18:09             ` Greg White
2014-04-30  3:21           ` Dave Taht
2014-04-30  6:53           ` Jan Ceuleers
2014-04-30  8:19             ` Pedro Tumusok [this message]
2014-04-30  8:30             ` Mikael Abrahamsson
2014-04-29 17:02         ` Dave Taht
2014-04-30  6:16         ` Mikael Abrahamsson
2014-04-29  7:43   ` Tristan Seligmann
2014-04-29 23:01 Hal Murray
2014-04-29 23:26 Michael Spacefalcon
2014-04-29 23:56 ` Steinar H. Gunderson
2014-04-30  0:14 ` Hal Murray

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='CACQiMXb4sG_VA=a-TGnKvnGrGfdXTebm2qoWVhYsw+dG=cNN+Q@mail.gmail.com' \
    --to=pedro.tumusok@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jan.ceuleers@gmail.com \
    /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