(In reply to James Fehlig from comment #7) > BTW, as the comments say in > /usr/lib/systemd/system.conf.d/__20-defaults-SUSE.conf, don't edit that file > directly. But the comments are not exactly clear on where the drop-in needs > to be placed. See also (numeric prefix suggestions) - https://en.opensuse.org/Systemd#Main_Configuration_files - https://documentation.suse.com/sles/15-SP5/html/SLES-all/cha-systemd.html#sec-boot-systemd-custom-drop-in (In reply to James Fehlig from comment #11) > I can only say there are penalties as per the comment in > /usr/lib/systemd/system.conf.d/__20-defaults-SUSE.conf. Perhaps Michal can > shed some light. Universal answer in [1]. As for memory controller -- it's workload and nr_cpus (contention/parallelism) dependent (as always). A targeted microbenchmarks saw below 10% drop. I believe in real workloads it will be diluted and negligible unless you want to squeeze every last cycle and byte (memcgs also need memory for themselves) of the machine. Partitioning memory into (accounting) cgroups affects reclaim, that may affect interference between jobs on the machine (which would be again workload dependent but it generally makes sense using memcgs between containers). [1] https://documentation.suse.com/sles/15-SP5/html/SLES-all/cha-tuning-cgroups.html#sec-tuning-cgroups-accounting