From: Loganaden Velvindron <loganaden@gmail.com>
To: moeller0 <moeller0@gmx.de>
Cc: Jonathan Morton <chromatix99@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] fq_codel on 3g network in Mauritius
Date: Sun, 24 Jul 2016 23:43:10 +0400 [thread overview]
Message-ID: <CAOp4FwT433Fv60KA8SswtmoF6jTjfKvTR3k2_GPLOBk7YNWXsA@mail.gmail.com> (raw)
In-Reply-To: <001B301F-5F3D-4751-A252-ED67021B0BC2@gmx.de>
>>
>> It's interesting to see the saw tooth pattern for the upload. This was
>> not the case when the target was 5ms, which I believe was calculated
>> based on a 100ms worse rtt.
>
>
> I just noticed you use the dslreports pre-canned profiles for measuring. I would recommend against doing that. As these will use different number of upstream/downstream flows per profile making comparisons between different profiles harder. I would recommend to get a free dslreports account and use the speed test configuration to use a fixed number of flows per direction (I typically use 16/16, but on slower links often I do not get all 16 going, in that case I retry with a lower number of flows, also set manually). After registration you can also request high resolution buffer bloat measurements, which nicely illustrate a link’s behavior under load (but might not work well on very slow links, so maybe you are already running the optimum configuration).
Thank you.
I did so, and here's the latest result:
https://www.dslreports.com/speedtest/4524841
It varies greatly. I think that it's due to the nature of the 3g connection.
next prev parent reply other threads:[~2016-07-24 19:43 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
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 [this message]
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=CAOp4FwT433Fv60KA8SswtmoF6jTjfKvTR3k2_GPLOBk7YNWXsA@mail.gmail.com \
--to=loganaden@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=moeller0@gmx.de \
/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