From: Dave Taht <dave.taht@gmail.com>
To: Noven Purnell-Webb <noven@liberant.com.au>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake over satellite
Date: Mon, 19 Oct 2015 16:58:55 +0200 [thread overview]
Message-ID: <CAA93jw7-YkCLct2STh+cPJOBiQyBNsSzsF6v3HRJD=LvydQstw@mail.gmail.com> (raw)
In-Reply-To: <CAGgan9pgcMBZRhxAuHAQxw07Bi3E7tzQObcvMYMiqEb6ZJAYDw@mail.gmail.com>
The current github/dtaht/sch_cake now has support for setting the rtt
(interval) parameter.
However, testing was to start... today. Taking it right to the outback
before then, well, that's a level of field test that I desire but...
wow!
On Mon, Oct 19, 2015 at 4:55 PM, Noven Purnell-Webb
<noven@liberant.com.au> wrote:
> I'm about to go on a mission to the outback, with one objective being to
> tune a disappointing satellite link. Theoretically 6/1mbps, with RTTs
> ranging from 700 - 1200ms. From the cake technical page
> "The AQM layer has no configuration options. However, it is planned to add
> simple tuning options for different prevailing RTTs that may be
> significantly different from the Internet-scale 100ms currently assumed.
> Satellite links tend to impose longer RTTs, and enclosed LANs tend to have
> much shorter RTTs." Does this imply cake is not yet ready for use on
> satellite links? Or merely that I'll get sub-optimal results but it's still
> worth testing?
> I see I could set the interval in sch_cake.c and recompile - is there any
> reason why this would be a bad idea? Am I right in thinking with such
> observed variation I'll get better results setting for the lower limit (700)
> rather than the upper (1200)?
> Any suggestions for a more sane target to set while I'm doing this?
> Has anyone here already done testing on satellite links?
>
> - Noven
>
> --
> - Noven Purnell-Webb
> Creative Technology Consultant
> +61 448 841 091
> http://onecardme.com/NovenPWebb
>
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
--
Dave Täht
Do you want faster, better, wifi? https://www.patreon.com/dtaht
next prev parent reply other threads:[~2015-10-19 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 14:55 Noven Purnell-Webb
2015-10-19 14:58 ` Dave Taht [this message]
2015-10-19 14:59 ` Loganaden Velvindron
2015-10-19 15:15 ` Sebastian Moeller
2015-10-19 15:24 ` Dave Taht
2015-10-19 19:05 ` Sebastian Moeller
2015-10-20 17:32 ` Kevin Darbyshire-Bryant
2015-10-21 1:26 ` Benjamin Cronce
2015-10-21 1:31 ` Jonathan Morton
2015-10-23 7:58 ` Sebastian Moeller
2015-10-19 15:48 ` Kevin Darbyshire-Bryant
2015-10-19 19:58 ` Sebastian Moeller
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='CAA93jw7-YkCLct2STh+cPJOBiQyBNsSzsF6v3HRJD=LvydQstw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=noven@liberant.com.au \
/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