Contents
Is there a limit to cgroups memory usage?
The default is max, meaning there is no limit. memory.max is the memory usage hard limit, acting as the final protection mechanism: If a cgroup’s memory usage reaches this limit and can’t be reduced, the system OOM killer is invoked on the cgroup. Under certain circumstances, usage may go over the memory.high limit temporarily.
What do you need to know about cgroup v2?
cgroup v2 supports thread granularity for a subset of controllers to support use cases requiring hierarchical resource distribution across the threads of a group of processes.
Where can I find Control Group v1 documentation?
Documentation for v1 is available under Control Groups version 1. “cgroup” stands for “control group” and is never capitalized. The singular form is used to designate the whole feature and also as a qualifier as in “cgroup controllers”. When explicitly referring to multiple individual control groups, the plural form “cgroups” is used.
What happens to anonymous memory in a cgroup?
If a cgroup’s swap usage reaches this limit, anonymous memory of the cgroup will not be swapped out; memory that already has swap slots allocated to it can continue to be swapped out. The default is max. Memory contention between system binaries and the main workload was one of the most common causes of resource problems.
What happens when a cgroup goes over a boundary?
If a cgroup’s memory use goes over the high boundary specified here, the cgroup’s processes are throttled and put under heavy reclaim pressure. The default is max, meaning there is no limit.
Why is it important to use cgroup2 memory controller?
Memory utilization is a key area where resource control can make big efficiency improvements. In this section we’ll look in detail at the cgroup2 memory controller, and how to get started configuring its interface files for controlling system memory resources.