From: Jonathan Morton <chromatix99@gmail.com>
To: Shefali Gupta <shefaligups11@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] COBALT implementation in ns-3 with results under different traffic scenarios
Date: Mon, 21 Jan 2019 14:57:47 +0200 [thread overview]
Message-ID: <4F9FBE72-2D10-4A9B-8662-EB1691C935F6@gmail.com> (raw)
In-Reply-To: <CAFp5xQ6mH9HD57wc00b+PO=nsH+Wo_B_zdwkeu70wsr2GTdwZA@mail.gmail.com>
> On 21 Jan, 2019, at 1:35 pm, Shefali Gupta <shefaligups11@gmail.com> wrote:
>
> We re-looked into the COBALT implementation to understand why it drops the first packet later than CoDel.
>
> There was a bug in the data that was collected in 'drop timestamp files'. We tried using a different approach to store packet drop times, and now we see that COBALT indeed drops the first packet prior to CoDel's first packet drop (image below). So the issue was that our previous approach of storing the packet drop times in a file was not correct.
>
> Let us know your opinion.
Okay, good catch.
But the more serious problem is with the pattern of drops, which presently looks much more like BLUE activity (random) than Codel (ramping frequency). That seems to be unchanged in your new graph.
Have you made any progress towards finding out why the queue is apparently too short? Perhaps log the actual length of the queue when overflow drops occur.
- Jonathan Morton
next prev parent reply other threads:[~2019-01-21 12:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 13:57 Jendaipou Palmei
2018-11-22 15:32 ` Dave Taht
2018-11-23 10:52 ` Jendaipou Palmei
2018-11-23 16:05 ` Dave Taht
2018-11-23 16:43 ` Dave Taht
2018-11-23 17:13 ` Jonathan Morton
2018-11-24 2:59 ` Jonathan Morton
2018-11-25 6:22 ` Jendaipou Palmei
2018-11-27 14:10 ` Jendaipou Palmei
2018-11-27 14:36 ` Jonathan Morton
2018-11-30 11:53 ` Jendaipou Palmei
2018-11-30 11:58 ` Jonathan Morton
2018-12-04 10:31 ` Jendaipou Palmei
2018-12-04 14:39 ` Dave Taht
2018-12-04 15:02 ` Jonathan Morton
2018-12-04 15:20 ` Dave Taht
2018-12-05 12:23 ` Jendaipou Palmei
2018-12-05 14:23 ` Jonathan Morton
2018-12-06 17:36 ` Jonathan Morton
2018-12-09 8:37 ` Jendaipou Palmei
2018-12-09 13:21 ` Jonathan Morton
2018-12-10 12:30 ` Jendaipou Palmei
2018-12-10 15:15 ` Jonathan Morton
2018-12-15 19:06 ` Shefali Gupta
2018-12-15 20:10 ` Dave Taht
2018-12-21 10:37 ` Shefali Gupta
2018-12-21 12:48 ` Jonathan Morton
2019-01-21 11:35 ` Shefali Gupta
2019-01-21 12:57 ` Jonathan Morton [this message]
2019-01-23 16:19 ` Shefali Gupta
2019-01-23 16:23 ` Jonathan Morton
2019-01-23 17:27 ` Shefali Gupta
2019-01-25 8:35 ` Shefali Gupta
2019-01-25 9:16 ` Jonathan Morton
2019-01-25 14:48 ` Shefali Gupta
2019-01-25 15:07 ` Jonathan Morton
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=4F9FBE72-2D10-4A9B-8662-EB1691C935F6@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=shefaligups11@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