Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: ecn-sane@lists.bufferbloat.net
Subject: [Ecn-sane] fq_codel_fast ECN signals vs number of flows
Date: Wed, 20 Mar 2019 19:49:05 +0100	[thread overview]
Message-ID: <70B7A260-EFBC-4556-88E5-B241C4B7ADA9@heistp.net> (raw)

Plots of congestion signals for increasing numbers of iperf3 flows:

https://www.heistp.net/downloads/fqf_nflows/

Most of it is expected. SCE signals start earlier than CE. As you increase the number of flows the number of CE signals increases, and SCE signals decrease until eventually all packets have CE markings and SCE is not used.

It’s still surprising though that with one flow that there’s really just one CE signal then that’s it, yet the rate is limited without drops. Is that somehow caused by TSQ?


             reply	other threads:[~2019-03-20 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 18:49 Pete Heist [this message]
2019-03-20 18:54 ` 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/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=70B7A260-EFBC-4556-88E5-B241C4B7ADA9@heistp.net \
    --to=pete@heistp.net \
    --cc=ecn-sane@lists.bufferbloat.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