←back to thread

Linux Network Performance Ultimate Guide

(ntk148v.github.io)
196 points bratao | 1 comments | 27 Jul 24 01:17 UTC | HN request time: 0s | source
Show context
dakiol ◴[27 Jul 24 08:23 UTC] No.41085214[source]▶
I find this cool, but as a software engineer I rarely get the chance to run any of the commands mentioned in the article. The reason: our systems run in containers that are stripped down versions of some Linux, and I don’t have shell access to production systems (and usually reproducing a bug on a dev or qa environment is useless because they are very different from prod in terms of load and the like).

So the only chance of running any of the commands in the article are when playing around with my own systems. I guess they would be useful too if I were working as Platform engineer.

replies(2): >>41085321 #>>41086157 #
1. znpy ◴[27 Jul 24 12:29 UTC] No.41086157[source]▶
Most of the low level stuff wouldn’t work or would be useless anyway, as most container network interface implementation will make you work with veth pairs and will do many userspace monstrosities.

This is one of the things I don’t like much about kubernetes: the networking model assume you only have one nic (like 99.99999% of cloud instances from cloud providers) and that your application is dumb enough not to need knowledge of anything beneath.

The whole networking model could really get a 2020-era overhaul for simplification and improvement.