From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: [Ecn-sane] containers and network namespaces
Date: Mon, 27 May 2019 08:21:11 -0700 [thread overview]
Message-ID: <CAA93jw7iaZQ0zqCaQsXyuXsNc97BOeFVBsr9Vp8ZLJjR7SpHFg@mail.gmail.com> (raw)
While in barcelona, I went to the *enormous* containercon conference,
5000+ attendance, tons and tons of people using docker, and I learned
for the first time the enormous size of the kubernetes deployment. The
website claims several billion containers are run every week, which I
do not doubt (how many are in active use at any one time would be a
good number to get)
So I sat down and said... hmmm... what if I had a netperf/irtt
container I could toss around for testing bufferbloat issues? It's not
clear to me, either, how often network namespaces are used in the
field(?) out of that billions deployment, but here a few months back,
I had showed the issues network namespaces had (at that point in time)
with self-congesting on overload:
https://github.com/systemd/systemd/issues/9725#issuecomment-413369212
Anyway, if anyone here has any data or has ever setup a container for
bufferbloat work, and wants to share?
I put the same question up over on their website, here:
https://discuss.kubernetes.io/t/self-congestion-fq-codel-bufferbloat-network-namespaces-and-containers/6533
If there's a better place to ask the question, please let me know?
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next reply other threads:[~2019-05-27 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 15:21 Dave Taht [this message]
2019-05-28 7:13 ` Mikael Abrahamsson
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7iaZQ0zqCaQsXyuXsNc97BOeFVBsr9Vp8ZLJjR7SpHFg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=ecn-sane@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