From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D9D033CB35 for ; Mon, 17 Feb 2020 09:34:41 -0500 (EST) Received: by mail-il1-x135.google.com with SMTP id g12so14430363ild.2 for ; Mon, 17 Feb 2020 06:34:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=TEa1LPKQfuRvwnbSM82OVrxWP+UtsRotmXKV8xJluE4=; b=Tr5OJnjNC0S44TqNxckAk4i+cihfM8sSj9pTmYgNNwjn/Cqdct9vWxNEZcRCGjk/DU H8iJe+gtl9MG6wweMTPNsCLGl2VaPGiFxk3GENOY8Y5A25FWLXxY6JW/h2Pg2lpnwsAl t49D/3tUk8PCTLtryq5pX4ItDKkiJNyiZ+YlYzv9Mr2jH31PtdEMQvgr1V1xlMC4L2bM WTUmJLY8EFg0MPSInFm1WHWjmjYlBi+9HXmDZ6OOIIVMIxBcw1hXwHEVakFzL8/rERcM Xz8Yi65pVCgGwLzcaLpd/IoWoKp1KtdaW+5eyJ+FbTaLOwijIdfo1RZcGmkfRK/3h9dF 1UKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=TEa1LPKQfuRvwnbSM82OVrxWP+UtsRotmXKV8xJluE4=; b=C3NV0NT2KS/MkRpFSnGF/LcOzfAlaL0twtrjMJ3tONcA/dqW7H/U1XW6Zi4l1ZErR8 H4JarQk1lMxW3WKkEyFopigYVaRyKqvLMwIR+OsmbYRAIS8BOtYMz2VqOT4u2oRrtDOL Tb3xtT1VwR/AxTWAFjlQpwjJlCrsugabTJv+r4lMtfsf+w6ocxHk/FMXn2bFRGIyT2p6 YslfZ27R3AbuJOxYs0+cdViOkwvPJsGufoiUd1WWCXphgfmVQiIQFrtalWP7efc/5RkA wWy7xwP07xDd5DhiLTcf8FBkvNCHGjLbKqVWtYgBLJgWOOF1uCK06ib0NVjngRiu4kDB veAw== X-Gm-Message-State: APjAAAWSfOC7M8Ucvp+b0ZSYh739020QUjby7XXo4JcY0I2W+AoKRQNU Fbr/vs6Eskd9Uxtt8HEQF6xKJTrGEqUuJZ60M1WjoA== X-Google-Smtp-Source: APXvYqz1Js1wAfD/wo7bjhtZibhlQUqqXlnN+zofcZOibJMBXbcmscworiX5JF7pgk2G+G+ygqSYjHUVOkiEs1UapB4= X-Received: by 2002:a92:85d2:: with SMTP id f201mr15554786ilh.45.1581950081255; Mon, 17 Feb 2020 06:34:41 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dave Taht Date: Mon, 17 Feb 2020 06:34:29 -0800 Message-ID: To: Mike Cc: Cake List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] Large number of Flows X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2020 14:34:42 -0000 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 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 c= ake 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 --=20 Make Music, Not War Dave T=C3=A4ht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-435-0729