From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 3DDC43CB3B for ; Fri, 23 Nov 2018 11:05:33 -0500 (EST) Received: from dancer.taht.net (unknown [IPv6:2603:3024:1536:86f0:eea8:6bff:fefe:9a2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 7CD1C21456; Fri, 23 Nov 2018 16:05:31 +0000 (UTC) From: Dave Taht To: Jendaipou Palmei Cc: dave.taht@gmail.com, cake@lists.bufferbloat.net References: Date: Fri, 23 Nov 2018 08:05:19 -0800 In-Reply-To: (Jendaipou Palmei's message of "Fri, 23 Nov 2018 16:22:06 +0530") Message-ID: <87va4nzsn4.fsf@taht.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] COBALT implementation in ns-3 with results under different traffic scenarios X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2018 16:05:33 -0000 Jendaipou Palmei 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. 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?=20 Care to try 100mbit? 20ms RTT? 80ms? :) Can you put your test code up somewhere? > > Thanks for your help.=20 > > On Thu, Nov 22, 2018 at 9:02 PM Dave Taht 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 > 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 >=20=20=20=20 > > > > 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 >=20=20=20=20=20 >=20=20=20=20=20 >=20=20=20=20=20 > --=20 >=20=20=20=20=20 > Dave T=C3=A4ht > CTO, TekLibre, LLC > http://www.teklibre.com > Tel: 1-831-205-9740