From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 901873BA8E for ; Tue, 4 Dec 2018 05:32:04 -0500 (EST) Received: by mail-wr1-x42b.google.com with SMTP id x10so15340181wrs.8 for ; Tue, 04 Dec 2018 02:32:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RzAV+dwpXOtu5p1k2xh0Dq9DVAfvQXkp9VmrpbLiwX4=; b=UZ9PBIEpU9ZWVTdXPhsJABapTIgYf2/Ngxo469sVy9vGguPqOSqGeJeUu6+X7u/stc ST268FUuT6Yd7aOjExoMvrzHAuxvpKVo43qW9aWVkJYel8CqgvAnWNtMC+7Oi0X0SNFC 0iYhHppcWqfLg35fYllmA+nxhyJUzARqf39Xn3HQBqizkpFoUfs0LssOPXqZv82DJ3AH gyYoVYCaiM4HhAkA2bD3YN2v5jIYu5OWlmRo3RdNwCRkoABcEjdzN86et5vf+GJ0ecvz 1x2Q/6iGXHe4hVSTKIZa95kc3/Ty6JBpWdfOLaFAAeljGemqmHicohoKgOZp01mWRzhE menQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RzAV+dwpXOtu5p1k2xh0Dq9DVAfvQXkp9VmrpbLiwX4=; b=IjPIJ/rLhi7vR3OjSi3jVhiUuariMbBQS60fMviJfC/YMkLQd0GaYvYdI1y40AssWg VZ01gUcb7vb4bJVKPHs0/wtf5ei1Dip1wtpaj8rZKf2ESh7I+St4d594GlX2R0ECyVTd 9nJ0E54f5lgjCvLh/pXWuk24KQVRjC/MmahPqmdtl2uxtgQ+2cLCuBCoNFwiEBeqvS1s cXss6+tBotmHRRN4kT9deDtqbti00HziJSws7Ua1XS1kv83kkoevcT/IUMhZRRKqBx5q AThNDi8nLTG6hwqY9E7mNCYtNn4BKqeMuaaDWfiaBt5O831bJBkWLre2R3uOxYMEo3/A j34A== X-Gm-Message-State: AA+aEWa8pBNFrNU1BWNImsgjfFkyyaQa4qcIy3rC/TDfC7xl1BqkiWCG 5i7ndltAW9PGSY4XQwetl3lJmqsZy/lecc6XZVs= X-Google-Smtp-Source: AFSGD/UCnBatTiQeofiJ0tgrZKXU/ljFIoGxcF2RQ1OBp5jV0Ypr1zbjylwQGN0kUQgIzqWACVfbBWpEdl9FdzR6QWw= X-Received: by 2002:adf:eec9:: with SMTP id a9mr17015638wrp.242.1543919523484; Tue, 04 Dec 2018 02:32:03 -0800 (PST) MIME-Version: 1.0 References: <87va4nzsn4.fsf@taht.net> <6578A0D1-FF6A-474E-A6D5-98185F98CB45@gmail.com> <08381337-F99A-46D1-87AF-B0F71A8753BC@gmail.com> In-Reply-To: <08381337-F99A-46D1-87AF-B0F71A8753BC@gmail.com> From: Jendaipou Palmei Date: Tue, 4 Dec 2018 16:01:26 +0530 Message-ID: To: chromatix99@gmail.com Cc: Dave Taht , dave@taht.net, cake@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="000000000000c25826057c2fc651" 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: Tue, 04 Dec 2018 10:32:04 -0000 --000000000000c25826057c2fc651 Content-Type: text/plain; charset="UTF-8" Hello Jonathan, Thanks for the quick reply. We have uploaded the plots for the 'count' variable of COBALT (with a segment size of 1500 and 1000 bytes). Link: https://github.com/Daipu/COBALT/wiki/Cobalt-Drop-Count We have not yet implemented ECN feature in COBALT, so packets are currently dropped instead of being marked. Are these the plots that you were referring to? Thanks and Regards Jendaipou Palmei Shefali Gupta On Fri, Nov 30, 2018 at 5:28 PM Jonathan Morton wrote: > > On 30 Nov, 2018, at 1:53 pm, Jendaipou Palmei > wrote: > > > > However, we finally noticed that it was the packet size used in our > simulations that was affecting the throughput. It was earlier set to 1000 > bytes, and after making it 1500 bytes (including headers) we note that the > throughput is not affected. > > > > We have uploaded the new graphs on the same wiki link: > > https://github.com/Daipu/COBALT/wiki/Light-Traffic > > > > We're not sure why packet size is affecting the throughput so largely. > Is it the expected behavior? > > That particular effect is probably accidental. > > Is it possible to also show graphs of the packet marking (or dropping) > rate? That may be revealing. > > - Jonathan Morton > > --000000000000c25826057c2fc651 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Jonathan,
Thanks=C2=A0for=C2=A0the quick reply.

We = have uploaded the plots for the 'count' variable of COBALT (with a = segment size of 1500 and 1000 bytes).


We have not yet implemented ECN feature in COBALT, so pack= ets are currently dropped instead of being marked.

Are these the plots that you were referring to?

T= hanks and Regards
Jendaipou Palmei
Shefali Gupta

On Fri, Nov 30, 20= 18 at 5:28 PM Jonathan Morton <= chromatix99@gmail.com> wrote:
jendaipoupalmei@gmail.com&= gt; wrote:
>
> However, we finally noticed that it was the packet size used in our si= mulations that was affecting the throughput. It was earlier set to 1000 byt= es, and after making it 1500 bytes (including headers) we note that the thr= oughput is not affected.
>
> We have uploaded the new graphs on the same wiki link:
> https://github.com/Daipu/COBALT/wiki/Light-Tr= affic
>
> We're not sure why packet size is affecting the throughput so larg= ely. Is it the expected behavior?

That particular effect is probably accidental.

Is it possible to also show graphs of the packet marking (or dropping) rate= ?=C2=A0 That may be revealing.

=C2=A0- Jonathan Morton

--000000000000c25826057c2fc651--