4 ms·
In some of our scaling test where each container had an IP connecting out to a remote system we ran in to a ton of issues at scale that we did not see running t
by myrandomcomment 9y ago
In some of our scaling test where each container had an IP connecting out to a remote system we ran in to a ton of issues at scale that we did not see running the same number of processes on the bare metal. The overhead of the namespace can add up.
- nwmcsween 9y agoThis is due to the what the container orchestratior uses to route traffic, check out project calico for low overhead networking.
- myrandomcomment 9y agoThe issue had everything to do with how Linux handles networking when you have 1000 container interfaces on a single system. Tweaking net.ipv4.neigh.default.gc* solved most of the issues. I am familiar with Calico and it would not have solved it.