Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
* [Ecn-sane] containers and network namespaces
@ 2019-05-27 15:21 Dave Taht
  2019-05-28  7:13 ` Mikael Abrahamsson
  0 siblings, 1 reply; 2+ messages in thread
From: Dave Taht @ 2019-05-27 15:21 UTC (permalink / raw)
  To: ECN-Sane, bloat

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-05-28  7:13 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-27 15:21 [Ecn-sane] containers and network namespaces Dave Taht
2019-05-28  7:13 ` Mikael Abrahamsson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox