Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] cctrace prototype
Date: Wed, 20 Mar 2019 05:42:19 +0200	[thread overview]
Message-ID: <196CD487-B489-4C13-A13A-D005DE0457C5@gmail.com> (raw)
In-Reply-To: <4D0CB5F2-93DD-4072-81C8-96F8ECAC870D@heistp.net>

> On 20 Mar, 2019, at 2:41 am, Pete Heist <pete@heistp.net> wrote:
> 
> So I’m starting work on a tool to make congestion signal plots in xplot.org format. It’s in Go for now and reads pcap files, producing one plot for each flow of the timestamp vs signal proportion. I’ll merge it to tcptrace later if needed, this is just faster for getting it started.
> 
> Here are screenshots and xpl files of one flow from a 10 second, 16-flow iperf upload with fq_codel_fast:
> 
> https://www.heistp.net/downloads/cctrace/
> 
> For each point, right arrow is used for upstream and left for downstream.
> 
> You can see that the SCE signals start sooner before CE takes over, which could theoretically prevent CE with a cooperating TCP.

Well, it's not *very* easy to see - but that is the idea in theory.  It might be easier to analyse such things (at this early stage of development) with a single flow, or possibly a pair with staggered start times.

One thing I'm noticing is that the SCE rate drops off very sharply when the CE marking rate rises, but the latter doesn't read higher than 50%.  Check your axis scale and your window average function for fenceposts.

> It needs some work, and I’m not yet satisfied with the windowing behavior. Choose a window size too low and the proportion value is visibly quantized. Too high and changes aren’t well reflected. I might be able to make a reasonable choice automatically through.
> 
> Thoughts? Ok to discuss this on ecn-sane?
> 
> Also, feel free to imagine what else would help visualize CC (different plot entirely? combined with throughput / RTT / TCP window?) and I’ll try to make it happen...

I'd like to see a sequence plot with the ECN codepoint indicated by colour coding, and similarly for ECE/NS/CWR on the ack path.

I'd also like to see a dynamic estimate of cwnd (or rather, in-flight data), with similar colour coding and/or labelling, for correlation.

 - Jonathan Morton


       reply	other threads:[~2019-03-20  3:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D0CB5F2-93DD-4072-81C8-96F8ECAC870D@heistp.net>
2019-03-20  3:42 ` Jonathan Morton [this message]
2019-03-20  7:20   ` Pete Heist
2019-03-20 10:11     ` Pete Heist

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=196CD487-B489-4C13-A13A-D005DE0457C5@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=pete@heistp.net \
    /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