From: moeller0 <moeller0@gmx.de>
To: Loganaden Velvindron <loganaden@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] fq_codel on 3g network in Mauritius
Date: Sun, 24 Jul 2016 10:27:25 +0200 [thread overview]
Message-ID: <04080AE6-8C47-4224-8DE3-BA374CBE38F5@gmx.de> (raw)
In-Reply-To: <CAOp4FwQ5D3u51jbTV8U11X2Bx4QVtvK+Qbp1UwCzq0B1miRdHQ@mail.gmail.com>
Hi Loganaden,
this is exactly the right idea; interval basically defines the “reaction time” window, or the time the endpoints of a connection minimally require to actually react to the drop/mark signal. So on a slow link with RTTs in the order of 300ms set interval to 300ms.
Target should be set to around 5-10% of interval to optimze the bandwidth latency tradeoff, but in any case target should be larger than the time required to send an individual packet, so that no queue builds up for sparse flows.
It is not quite clear to me whether in your case you would account the long “pipeline” depth to the target or simply bandwidth/1540…
Best Regards
Sebastian
> On Jul 24, 2016, at 09:03 , Loganaden Velvindron <loganaden@gmail.com> wrote:
>
> I am getting A to A+ for quality when setting the interval to 350ms.
>
> http://www.dslreports.com/speedtest/4520977
>
> I am getting - to C for quality when setting the interval to the
> default value of 100ms.
>
> http://www.dslreports.com/speedtest/4520957
next prev parent reply other threads:[~2016-07-24 8:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 4:29 Loganaden Velvindron
2016-07-19 8:09 ` Jonathan Morton
2016-07-19 10:16 ` moeller0
[not found] ` <CAOp4FwQs9-PF=V5zDDMVj_38qmziKkeZECTyX1e8EfChtGm8bA@mail.gmail.com>
[not found] ` <7ECE7E7A-0310-4DC4-8AC9-29B0F1F2E383@gmx.de>
2016-07-23 18:36 ` Loganaden Velvindron
2016-07-23 18:59 ` Loganaden Velvindron
2016-07-24 5:53 ` Loganaden Velvindron
2016-07-24 6:12 ` Loganaden Velvindron
2016-07-24 7:03 ` Loganaden Velvindron
2016-07-24 8:27 ` moeller0 [this message]
2016-07-24 8:43 ` Loganaden Velvindron
2016-07-24 10:53 ` moeller0
2016-07-24 11:28 ` Jonathan Morton
2016-07-24 14:40 ` moeller0
2016-07-24 16:18 ` Jonathan Morton
2016-07-24 17:13 ` Loganaden Velvindron
2016-07-24 17:21 ` moeller0
2016-07-24 19:43 ` Loganaden Velvindron
2016-07-25 4:13 ` Loganaden Velvindron
2016-07-26 21:10 ` Loganaden Velvindron
2016-07-30 3:45 ` Loganaden Velvindron
2016-07-30 13:04 ` Mario Ferreira
2016-07-30 13:48 ` Loganaden Velvindron
2016-07-30 14:07 ` Mario Ferreira
2016-08-03 18:52 ` Loganaden Velvindron
2016-08-03 19:48 ` David Lang
2016-07-19 17:13 ` Loganaden Velvindron
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=04080AE6-8C47-4224-8DE3-BA374CBE38F5@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=loganaden@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