Hello from Argentina! I am so thankful for your explain in the video, because: I use Arch Linux on my laptop for my studies as software developer, and it was very useful to evade that my machine freeze and I can't use it, unless press reboot button (that's the only option).
@nevyan Thanks for the video. I have a requirement to limit CPU and memory usage of a particular process using systemd and cgroup. Is there a separate video on this ? This limitation should apply to all users. Or is there a way to add my process name or id using the method shown in this video ?
I have a question. I am having aks cluster. So how i can actually check whether cgroup has been there and how to check if there is limit and request for pod has been there in cgroup. Can someone help plz
Do you know how to *easily* configure systemd to put all Google Chrome processes in a single memory cgroup and limit the max memory usage to 50% of the system RAM on Ubuntu? It used to be easy with cgmanager but that can no longer be used with systemd because systemd wants to control everything.
perhaps those ones could be of help: unix.stackexchange.com/questions/451577/limit-memory-for-browser-on-fedora unix.stackexchange.com/questions/659744/why-cant-cpulimit-limit-chromium-browser
@@NevyanNeykov Other than the example with `systemd-run` require using cgmanager which is no longer supported with recent systemd versions. And the `systemd-run` only works if that's the only way you actually launch that process.
Another possibility is to wrap the chromium process into a service where to use: MemoryMax to set the memory limit. On boot SystemD will auto start the service and apply the set limits to each new chromium instance.
@@NevyanNeykov How would you do that? Chromium requires a separate X display connection for each logged in user. With cgmanager it was simple to create one memory cgroup for Chrome/Chromium but with systemd there doesn't seem to be any simple way to do that.
From my case it was keeping the settings set, on one system I even had to reset them by setting them to -1. Depends on the systemd version I guess, otherwise you set them before provisioning the machine. From the docs: systemctl set-property - the adjustments will be made permanent unless --runtime option is passed.
