From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] fq_codel_fast
Date: Thu, 6 Sep 2018 11:40:11 -0700 [thread overview]
Message-ID: <CAA93jw4fV36S+Aa21soQL7RgtMGUTN=XhnQ97ifZ8rpRe=hHuw@mail.gmail.com> (raw)
In-Reply-To: <C9C84B23-FE6C-46D9-ADE0-AD52EBD8142C@heistp.net>
re: conntrack - I think the udp standard for holding a hole punch open
is 2-3 minutes. I've
seen 30 sec or less in the field.
On Thu, Sep 6, 2018 at 11:36 AM Pete Heist <pete@heistp.net> wrote:
>
>
> > On Sep 6, 2018, at 7:22 PM, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > There was a very good paper or two (I think luca co-authored one) that
> > showed that "active flows" were generally measured in the mid 200s in
> > nearly any scenario. I agreed with that which was in part why I felt
> > we could stick
> > with 1024 queues, a direct mapped hash, and a couple collisions.
>
> So I’m not sure if this is a great way to gauge active flow counts through a router, but at 8pm:
>
> root@FreeNetVysina:~# grep ESTABLISHED /proc/net/ip_conntrack | wc -l
> 446
> FreeNetJerab:~# grep ESTABLISHED /proc/net/ip_conntrack | wc -l
> 181
> FreeNetOldrichova:~# grep ESTABLISHED /proc/net/ip_conntrack | wc -l
> 228
>
> Far from my estimate of tens. Many of those can be idle connections, I suspect. 60-80% of them are http/s.
>
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-09-06 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 1:04 Dave Taht
2018-08-29 8:12 ` Pete Heist
2018-08-29 14:23 ` Dave Taht
2018-08-30 18:24 ` Dave Taht
2018-09-06 17:10 ` Pete Heist
2018-09-06 17:22 ` Dave Taht
2018-09-06 17:25 ` Sebastian Moeller
2018-09-06 18:36 ` Pete Heist
2018-09-06 18:40 ` Dave Taht [this message]
2018-09-06 18:42 ` Sebastian Moeller
2018-09-06 19:08 ` Toke Høiland-Jørgensen
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='CAA93jw4fV36S+Aa21soQL7RgtMGUTN=XhnQ97ifZ8rpRe=hHuw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=pete@heistp.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