From: Shefali Gupta <shefaligups11@gmail.com>
To: Jonathan Morton <chromatix99@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: Fri, 25 Jan 2019 20:18:50 +0530 [thread overview]
Message-ID: <CAFp5xQ5Wdds2kq_Lnf2LuXkzENFv6HLFSu54oB4ZW+1cOVTRyg@mail.gmail.com> (raw)
In-Reply-To: <FFA16736-4249-49BB-B2D5-8AB06A8B9200@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
Hello Jonathan,
We have added CoDel and PIE graphs for Heavy and Mix scenarios.
Link:
https://github.com/Daipu/COBALT/wiki/Heavy-Traffic
https://github.com/Daipu/COBALT/wiki/Mix-Traffic
Also we have added drop-event logs for the same scenarios.
Link:
https://github.com/Daipu/COBALT/wiki/Drop-Timestamp-Files
Thanks and Regards,
Shefali Gupta
Jendaipou Palmei
On Fri 25 Jan 2019, 2:46 p.m. Jonathan Morton <chromatix99@gmail.com wrote:
> > On 25 Jan, 2019, at 10:35 am, Shefali Gupta <shefaligups11@gmail.com>
> wrote:
> >
> > We have updated all the graphs with updated COBALT code and BQL enabled.
>
> The graphs available so far do show a big improvement in behaviour. Could
> you also add comparative data for Codel and PIE in the Heavy and Mix
> scenarios? It seems reasonable to also generate drop-event logs for those
> scenarios.
>
> - Jonathan Morton
>
>
[-- Attachment #2: Type: text/html, Size: 2580 bytes --]
next prev parent reply other threads:[~2019-01-25 14:49 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
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 [this message]
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=CAFp5xQ5Wdds2kq_Lnf2LuXkzENFv6HLFSu54oB4ZW+1cOVTRyg@mail.gmail.com \
--to=shefaligups11@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--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