From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Long-RTT broken again
Date: Sat, 7 Nov 2015 08:49:08 +0200 [thread overview]
Message-ID: <136640C5-58AD-4633-8021-6FAC374428B5@gmail.com> (raw)
In-Reply-To: <CAA93jw75vJU4vfbMB-BtzbgU+xYkJrgAqx79BY9-c8Yvt5ogiw@mail.gmail.com>
> On 7 Nov, 2015, at 07:16, Dave Taht <dave.taht@gmail.com> wrote:
>
> I note that truesize is a bad indicator for tests on the rx path where
> acks are usually 2k.
At least in my test setup, cake is on the egress side, so I would hope that doesn’t come into it. I’m putting netem on the ingress side and giving it a limit of 102400 packets, which hopefully is never hit:
cake bandwidth 100Mbit satellite -> GigE -> netem delay 500ms limit 102400
netem delay 500ms limit 102400 <- GigE <- cake bandwidth 100Mbit satellite
With that setup, I’m seeing very poor throughput with CUBIC (less than 10Mbit) but much better with Westwood+ (about 50Mbit) - of course that’s the opposite of the theoretical result. Next I’ll try increasing cake’s memory limit. Both machines are desktop-class (with 1GB and 16Gb RAM), so that won’t be a problem for experimenting.
- Jonathan Morton
next prev parent reply other threads:[~2015-11-07 6:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 16:53 Toke Høiland-Jørgensen
2015-11-02 18:29 ` Sebastian Moeller
2015-11-03 1:39 ` Jonathan Morton
2015-11-03 8:20 ` Sebastian Moeller
2015-11-03 8:25 ` Jonathan Morton
2015-11-03 8:34 ` Sebastian Moeller
2015-11-03 10:29 ` Kevin Darbyshire-Bryant
2015-11-03 11:08 ` Sebastian Moeller
2015-11-03 11:45 ` Toke Høiland-Jørgensen
2015-11-03 11:57 ` Toke Høiland-Jørgensen
2015-11-03 12:41 ` Sebastian Moeller
2015-11-03 11:50 ` Toke Høiland-Jørgensen
2015-11-03 16:43 ` Jonathan Morton
2015-11-03 17:05 ` Toke Høiland-Jørgensen
2015-11-03 17:11 ` Sebastian Moeller
2015-11-03 17:25 ` Toke Høiland-Jørgensen
2015-11-03 17:31 ` Jonathan Morton
2015-11-03 17:33 ` Toke Høiland-Jørgensen
2015-11-03 17:46 ` Sebastian Moeller
2015-11-03 17:49 ` Toke Høiland-Jørgensen
2015-11-03 17:52 ` Sebastian Moeller
2015-11-03 17:54 ` Toke Høiland-Jørgensen
2015-11-03 17:57 ` Sebastian Moeller
2015-11-03 17:59 ` Toke Høiland-Jørgensen
2015-11-03 18:06 ` Sebastian Moeller
2015-11-03 19:17 ` Jonathan Morton
2015-11-03 19:24 ` Sebastian Moeller
2015-11-05 14:36 ` Toke Høiland-Jørgensen
2015-11-05 19:30 ` Jonathan Morton
2015-11-06 11:00 ` Toke Høiland-Jørgensen
2015-11-06 14:15 ` Toke Høiland-Jørgensen
2015-11-06 15:09 ` Toke Høiland-Jørgensen
2015-11-07 5:02 ` Jonathan Morton
2015-11-07 5:16 ` Dave Taht
2015-11-07 6:49 ` Jonathan Morton [this message]
2015-11-07 8:48 ` Toke Høiland-Jørgensen
2015-11-07 10:51 ` Jonathan Morton
2015-11-07 13:06 ` Jonathan Morton
2015-11-07 13:42 ` Toke Høiland-Jørgensen
2015-11-07 16:34 ` Toke Høiland-Jørgensen
2015-11-07 13:44 ` Toke Høiland-Jørgensen
2015-11-07 15:08 ` Sebastian Moeller
2015-11-07 16:24 ` Toke Høiland-Jørgensen
2015-11-07 18:25 ` Sebastian Moeller
2015-11-07 19:32 ` Kevin Darbyshire-Bryant
2015-11-08 16:29 ` Dave Taht
2015-11-11 10:23 ` 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=136640C5-58AD-4633-8021-6FAC374428B5@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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