Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: [Cake] triple flow isolation
Date: Mon, 11 Jan 2016 17:40:10 +0000	[thread overview]
Message-ID: <5693E8FA.4000803@darbyshire-bryant.me.uk> (raw)

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

Hello List,

I've been looking at latest 'triple flow isolation' features in latest
cake git and find myself confused.  It's very likely to be a
misunderstanding on my part, although if I'm confused I'm sure others
will, sooner or later, fall into the same trap.

I thought that triple flow was a solution such that a host with many
elephant flows couldn't dominate the bandwidth consumption thus starving
another host with just one elephant flow.  I guess the typical example
is a 'bittorrent' host pulling data from many places vs a host pulling
data from a single place.  My recent 'test' example was a host doing 4
simulatenous pulls of 9GByte+ files vs my wife downloading a movie via
the TV box downstairs.  The bandwidth was evenly divided by the 5 flows,
however my host got 4/5ths of the share.  I didn't think this was
supposed to happen with triple flow isolation?  Ideally we'd both get
50% of the ISP bandwidth managed by my router (cake is running on the
WAN facing interface to the ISP modem with appropriate bandwidth limits set)

The good news is that latency was well controlled and general web
browsing/catching emails etc was oblivious to the elephant melee going on.

Advice gratefully received.


Kevin


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]

             reply	other threads:[~2016-01-11 17:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 17:40 Kevin Darbyshire-Bryant [this message]
2016-01-11 18:16 ` moeller0
2016-01-11 20:33   ` Kevin Darbyshire-Bryant
2016-01-14 14:20     ` moeller0
2016-01-14 14:45       ` Jonathan Morton
2016-01-14 15:48         ` moeller0
2016-01-14 16:05           ` Jonathan Morton
     [not found]             ` <02A10F37-145C-4BF9-B428-BC1BDF700135@gmx.de>
2016-01-15  0:05               ` Jonathan Morton
2016-01-15  8:05                 ` moeller0
2016-01-16  9:05                   ` Jonathan Morton
2016-01-16  9:35                     ` Jonathan Morton
2016-01-17 22:22                       ` moeller0
2016-01-18  9:21                     ` moeller0
2016-01-18  9:37                       ` Jonathan Morton
2016-01-18 11:08                         ` Alan Jenkins
2016-01-18 11:39                           ` Jonathan Morton
2016-01-18 16:20                         ` Sebastian Moeller

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=5693E8FA.4000803@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --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