From: Dave Taht <dave.taht@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: Jendaipou Palmei <jendaipoupalmei@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] COBALT implementation in ns-3 with results under different traffic scenarios
Date: Fri, 23 Nov 2018 08:43:43 -0800 [thread overview]
Message-ID: <CAA93jw55N1xBuJRkkO_pnHdNkHwTLR4aT8E6p8YkwTq0WQ=hjQ@mail.gmail.com> (raw)
In-Reply-To: <87va4nzsn4.fsf@taht.net>
On Fri, Nov 23, 2018 at 8:05 AM Dave Taht <dave@taht.net> wrote:
>
> Jendaipou Palmei <jendaipoupalmei@gmail.com> writes:
>
> > Hi Dave,
> >
> > We have added the results for CoDel and PIE in the same setup.
> >
> > Link:
> > https://github.com/Daipu/COBALT/wiki/Light-Traffic
>
> Wonderful, thank you. One new thing in cobalt is it responds much
> earlier to stuff in slow start, and thus that first spike is much
> smaller than it is with codel or pie. Network researchers spend way too
> much time looking at stuff in congestion avoidance mode, where what we
> see in the real world is most flows never get out of slow start.
>
> As an example, slashdot.org, last I checked, started 78 flows over 2.2
> seconds for a page load.
>
> I'm still puzzled as to why queue utilization spikes and drops so
> much on all three qdiscs in your simulation. In general we use a much
> larger number of packets in our packet limit (1000 or more) and I am
> thinking tail drop is controlling your queue more than any of the qdiscs
> are at 10mbit with a 50ms delay. I haven't had enough coffee yet this
> morning to do the bdp here, but that's another easy param to tweak.
this was definiately pre-coffee, you are showing next to no queue
utilization in the first place and good throughput on pie and codel.
It was the throughput graph I was mis-interpreting.
This is possibly a correct result in your simulation!! - the periodic
throughput drop you are showing in cobalt at this bandwidth and rtt.
I'm happy to see cobalt kick in early on slow start but not happy to
see the periodic drop. Jon, do you have time for a code review?
It also looks like we can setup a simple real-world duplicate of this
test in flent (5 flows) + netem. However (sigh), our tc sampler for
queue depth is broken on modern versions of iproute2.
Also the aqm work that I'd done on cake was eliminated in the rewrite,
and that I'd not gone at looked hard at longer rtts again, lacking
resources.
> Ns3, btw, also has fq_codel. I happen to be fond of what fq can do. if
> you feel like another run, with the packet limit increased and that
> added too?
>
> Care to try 100mbit? 20ms RTT? 80ms? :)
>
> Can you put your test code up somewhere?
>
>
> >
> > Thanks for your help.
> >
> > On Thu, Nov 22, 2018 at 9:02 PM Dave Taht <dave.taht@gmail.com> wrote:
> >
> > Your light traffic graph is puzzling, with the synchronized drops.
> > Is
> > it possible for you to do another test run, same setup, with codel
> > or
> > pie?
> > On Thu, Nov 22, 2018 at 5:57 AM Jendaipou Palmei
> > <jendaipoupalmei@gmail.com> wrote:
> > >
> > > Hello Jonathan and Dave,
> > >
> > > Thanks for your timely inputs.
> > >
> > > We have implemented COBALT in ns-3. The main C++ file is here:
> > >
> > >
> > https://github.com/Daipu/COBALT/blob/master/src/traffic-control/model/cobalt-queue-disc.cc
> >
> > >
> > > We have also added Queue length and Throughput graphs for COBALT
> > in our wiki:
> > >
> > > https://github.com/Daipu/COBALT/wiki
> > >
> > > Thanks and Regards,
> > > Jendaipou Palmei
> > > Shefali Gupta
> > > _______________________________________________
> > > Cake mailing list
> > > Cake@lists.bufferbloat.net
> > > https://lists.bufferbloat.net/listinfo/cake
> >
> >
> >
> > --
> >
> > Dave Täht
> > CTO, TekLibre, LLC
> > http://www.teklibre.com
> > Tel: 1-831-205-9740
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next prev parent reply other threads:[~2018-11-23 16:43 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 [this message]
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
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='CAA93jw55N1xBuJRkkO_pnHdNkHwTLR4aT8E6p8YkwTq0WQ=hjQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=jendaipoupalmei@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