Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] results of two simple ECN tests
Date: Mon, 18 Feb 2019 11:33:06 +0100	[thread overview]
Message-ID: <C096F1D2-4F02-4604-B3FB-9F08CF53FBF5@heistp.net> (raw)
In-Reply-To: <09043521-6078-42D3-A32E-CCAC94011F2C@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 2676 bytes --]


> On Feb 17, 2019, at 10:07 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
> 
> 	But in your test, a reduced TCP RTT should result in a higher throughput, no?

Theoretically, but I think the difference may be only marginal at modern bandwidths. For example, during my 20Mbit, 10 second “one vs one” iperf test, 23770 segments are sent and only 9 are dropped. ECN saves those 9 segments, but that’s only 13626 bytes (0.038%), plus what ever side effects there may be. My current test with iperf isn’t sensitive enough to measure a corresponding difference in throughput.

Note that at https://en.wikipedia.org/wiki/Explicit_Congestion_Notification#Effects_on_performance <https://en.wikipedia.org/wiki/Explicit_Congestion_Notification#Effects_on_performance>, it claims "Effects of ECN on bulk throughput are less clear”, which references a 2003 paper "Marek Malowidzki, Simulation-based Study of ECN Performance in RED Networks”.

>> I'll rather compare packet captures with it on and off to look for an improvement in the TCP RTT spikes typically associated with drops.
> 
> Well, the big danger of dropping packets is that you might stall a flow (say, by dropping enough consecutive packets to drive the flow into RTO) something much less likely with SACK (at least that is my understanding of one of SACKs promises).

That may be, but my simple simulation doesn’t reproduce that case. I’ve updated it and made some TCP RTT graphs, which does show a clearer difference with ECN. All the files and pcaps are here:

https://www.heistp.net/downloads/veth_ecn/ <https://www.heistp.net/downloads/veth_ecn/>

Compare these two one-vs-one RTT graphs and the difference with ECN enabled can be seen:

https://www.heistp.net/downloads/veth_ecn/client_one_vs_one_noecn_rtt.png <https://www.heistp.net/downloads/veth_ecn/client_one_vs_one_noecn_rtt.png>

https://www.heistp.net/downloads/veth_ecn/client_one_vs_one_ecn_rtt.png <https://www.heistp.net/downloads/veth_ecn/client_one_vs_one_ecn_rtt.png>

Similar for one-vs-pulses:

https://www.heistp.net/downloads/veth_ecn/client_one_vs_pulses_noecn_rtt.png <https://www.heistp.net/downloads/veth_ecn/client_one_vs_pulses_noecn_rtt.png>

https://www.heistp.net/downloads/veth_ecn/client_one_vs_pulses_ecn_rtt.png <https://www.heistp.net/downloads/veth_ecn/client_one_vs_pulses_ecn_rtt.png>

The graphs of TCP window are also more appealing in the ECN case, at least.

Now, re-reading Dave’s posts about why the ECN-sane project was started, there appear to be some pathological cases. This simple test doesn’t get to those. For now just wanted to get in touch with some basics. :)


[-- Attachment #2: Type: text/html, Size: 4019 bytes --]

  reply	other threads:[~2019-02-18 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 11:26 Pete Heist
2019-02-17 13:02 ` Sebastian Moeller
2019-02-17 20:57   ` Pete Heist
2019-02-17 21:07     ` Sebastian Moeller
2019-02-18 10:33       ` Pete Heist [this message]
2019-02-18 19:24         ` Dave Taht

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/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C096F1D2-4F02-4604-B3FB-9F08CF53FBF5@heistp.net \
    --to=pete@heistp.net \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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