Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Mike <mike@surfglobal.net>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Large number of Flows
Date: Mon, 17 Feb 2020 06:34:29 -0800	[thread overview]
Message-ID: <CAA93jw4wvP8OJAL6_XAZOO+wp36-Vbd4Rj9BvBd+_Tv8cjNexQ@mail.gmail.com> (raw)
In-Reply-To: <etPan.5e4a9b91.58a6c5a1.1b7f@surfglobal.net>

fq_codel, Cake etc, supports an infinite number of flows.

It has a limited number of "queues" that can get mapped to flows, but
it's usually ok if a collision happens.

The 1024 queue tradeoff is based on the observation that usually a max
of a few hundred active flows exist, and furthermore,
excessive fair queueing tends to defeat the purpose of the aqm of
keeping overall flow lengths short. Collisions of two fat flows are
rare.

You can recompile cake with more queues if you like (fq_codel has a
soft limit of 64k queues). We don't have much data on 10GigE+
behaviors. It was kind
of my assumption more queues would help in the 40GigE world, but
that's usually got hardware mq (64 or more), and what I'm seeing there
is 64 default fq_codel instances, 64k
queues essentially, and I think that's WAY too much....


On Mon, Feb 17, 2020 at 6:07 AM Mike <mike@surfglobal.net> wrote:
>
> Will cake support a large number of flows like over a thousand per linux box without any modifications.  I did see that there was a qdisc issue for fq_codel on a large scale.  We would be using linux kernel 4.19 which has cake already in it.  Any help or issues that might be encountered in scaling would be appreciated.
>
>
>
> Thanks
> Mike Thompson
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake



-- 
Make Music, Not War

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729

  reply	other threads:[~2020-02-17 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 13:56 Mike
2020-02-17 14:34 ` Dave Taht [this message]
     [not found]   ` <etPan.5e4ab6c5.653ea685.1b7f@surfglobal.net>
2020-02-17 18:21     ` 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=CAA93jw4wvP8OJAL6_XAZOO+wp36-Vbd4Rj9BvBd+_Tv8cjNexQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=mike@surfglobal.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