Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] lan keyword affects host fairness
Date: Thu, 23 Nov 2017 10:21:43 +0100	[thread overview]
Message-ID: <71FB183D-F848-4513-A6F6-D03FD0F10769@gmail.com> (raw)

It seems that the ‘lan’ keyword (and probably other lower rtt settings in general) may adversely impact host fairness in some cases. Is this to be expected? I set up a fairness test with rrul_be_nflows where one client has 2/2 TCP flows and the other has 8/8 TCP flows, then ran five tests:

https://docs.google.com/spreadsheets/d/1SMXWw2fLfmBRU622urfdvA_Ujsuf_KQ4P3uyOH1skOM/edit?usp=sharing

As can be seen, fairness works well with the default rtt, but with the lan keyword, it varies from partially fair when rate limiting is used to as if there’s no fairness at all when unlimited (bql) is used. So either we could find some problem with my test, or this may at least need to be documented somewhere...

Pete


             reply	other threads:[~2017-11-23  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23  9:21 Pete Heist [this message]
2017-11-23  9:44 ` Jonathan Morton
2017-11-23 10:25   ` Pete Heist
2017-11-23 17:03     ` Dave Taht
2017-11-24 11:21       ` Toke Høiland-Jørgensen
2017-11-24 12:06         ` Sebastian Moeller
2017-11-24 13:15           ` Marcelo Ricardo Leitner
2017-11-24 13:49         ` Pete Heist
2017-11-24 19:41           ` Pete Heist
2017-11-24 19:48             ` Jonathan Morton
2017-11-24 20:24               ` Pete Heist
     [not found]                 ` <CAJq5cE2eX4AJCPaBL-FW7Oj_afthXKnZn1RHQPH1VBCJfCyXDg@mail.gmail.com>
2017-11-24 20:32                   ` Jonathan Morton
2017-11-25  7:18                     ` Pete Heist
2017-11-24 20:03             ` Dave Taht
2017-11-24 20:40             ` 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/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=71FB183D-F848-4513-A6F6-D03FD0F10769@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@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