In a previous embedded job, I built a daemon watching a couple of “at risk of eating too much memory” processes that were not critical for the actual function o

In a previous embedded job, I built a daemon watching a couple of “at risk of eating too much memory” processes that were not critical for the actual function of the machine, and killed them proactively when memory started getting low. This prevented the system from going into starvation and spending 10 seconds doing whatever each time an Ethernet packet came in. As for my pragmatic solution at home: max out the physical RAM…