From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Christoph Paasch <cpaasch@apple.com>, Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] Alternate definitions of "working condition" - unnecessary?
Date: Fri, 8 Oct 2021 03:33:00 +0300 [thread overview]
Message-ID: <4223548E-7DD0-40B6-8CA0-107054BCF6F5@gmail.com> (raw)
In-Reply-To: <45E18E9B-DD71-4F8A-92C2-AB5AA4439DC0@gmx.de>
> On 7 Oct, 2021, at 1:30 pm, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> I am also wondering how reducing the default number of sub-queues from 1024 to 128 behaves on the background of the birthday paradox
With 1024 queues, the 50% probability of a collision is expected at sqrt(1024) = 32 flows. With 128, this decreases to about 11 or 12 flows (11*11 = 121; 12*12 = 144).
In both cases, onset of high collision probability could be staved off until a larger number of flows by using a collision-avoiding hash function, such as the set-associative hash used in Cake.
- Jonathan Morton
next prev parent reply other threads:[~2021-10-08 0:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 19:11 Rich Brown
2021-10-06 20:36 ` Jonathan Foulkes
2021-10-07 16:40 ` Toke Høiland-Jørgensen
2021-10-07 18:49 ` Dave Taht
2021-10-08 17:51 ` Toke Høiland-Jørgensen
2021-10-07 21:39 ` Rich Brown
2021-10-06 21:22 ` Dave Taht
2021-10-06 23:18 ` Jonathan Morton
2021-10-07 0:11 ` Christoph Paasch
2021-10-07 10:29 ` Jonathan Morton
2021-10-07 15:44 ` [Rpm] apple's fq_"codel" implementation Dave Taht
2021-10-07 10:30 ` [Rpm] Alternate definitions of "working condition" - unnecessary? Sebastian Moeller
2021-10-08 0:33 ` Jonathan Morton [this message]
2021-10-08 23:32 ` Christoph Paasch
2021-10-11 7:31 ` Sebastian Moeller
2021-10-11 9:01 ` Jonathan Morton
2021-10-11 10:03 ` Sebastian Moeller
2021-10-11 17:34 ` Christoph Paasch
2021-10-12 10:23 ` 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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4223548E-7DD0-40B6-8CA0-107054BCF6F5@gmail.com \
--to=chromatix99@gmail.com \
--cc=cpaasch@apple.com \
--cc=moeller0@gmx.de \
--cc=rpm@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