Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: "techicist@gmail.com" <techicist@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Configuring cake for VDSL2 bridged connection
Date: Wed, 24 Aug 2016 20:47:50 +0100	[thread overview]
Message-ID: <ee3d4316-21ce-a196-db58-36c63b41da00@gmail.com> (raw)
In-Reply-To: <CANiaOCn-7Hy5+nn43pSc72HXRK6P2rJJvwD6mK4OpB27sQ1LAQ@mail.gmail.com>

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

So you can read off (+calculate) overall throughput, in both directions.

And it looks like your latency under load rises by only about 2ms.  
That's the sort of thing we're aiming for.

Pure codel aims for 5ms, so I take it you're using fq_codel. And... yes

(1500 * 8) / 4_000_000 = 0.003

It takes 3ms to transmit a full packet in the slower direction. So when 
it's busy, ping can be delayed on average by 1.5ms (while the current 
packet is transmitted).  Something like that anyway.


On 24/08/16 20:33, techicist@gmail.com wrote:
> Thanks for the reply. I understand now 😀
>
> What can be taken from these graphs? I'm afraid I really am lost now.
>
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


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

  reply	other threads:[~2016-08-24 19:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 13:44 techicist
2016-08-23 14:27 ` moeller0
2016-08-23 15:13   ` techicist
2016-08-23 20:09     ` Sebastian Moeller
2016-08-24 17:01       ` techicist
2016-08-24 17:03         ` techicist
2016-08-24 17:03           ` techicist
2016-08-24 17:16             ` Alan Jenkins
2016-08-24 19:33               ` techicist
2016-08-24 19:47                 ` Alan Jenkins [this message]
2016-08-24 19:49                   ` Alan Jenkins
2016-08-25 14:53                     ` techicist
2016-08-26  8:14                       ` Alan Jenkins
2016-08-26 11:15                         ` techicist
2016-08-26 11:29                           ` moeller0
2016-08-26 11:32                             ` techicist
2016-08-27  7:43                               ` Alan Jenkins
2016-08-27 16:17                                 ` techicist
2016-08-27 17:48                                   ` Alan Jenkins
2016-09-14 20:06                                     ` techicist
2016-09-14 20:41                                       ` Kevin Darbyshire-Bryant
2016-09-14 20:48                                         ` Sebastian Moeller
2016-09-15  9:24                                           ` Kevin Darbyshire-Bryant
2016-09-15  9:43                                       ` techicist
2016-08-26 11:52                             ` Alan Jenkins
2016-08-26 12:04                               ` techicist
2016-08-27  7:31                                 ` Alan Jenkins
2016-08-24  8:52     ` Kevin Darbyshire-Bryant

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee3d4316-21ce-a196-db58-36c63b41da00@gmail.com \
    --to=alan.christopher.jenkins@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=techicist@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