Read the CPU quota (cgroup v2)
cpu.max is "quota period" in microseconds, max means no limit. To change it, use systemctl set-property
cat /sys/fs/cgroup/system.slice/<name>.service/cpu.max # "max 100000" = unlimited; "50000 100000" = 0.5 core
- tool
- cgroups8 commands
More cgroups commands
-
cat /sys/fs/cgroup/system.slice/<name>.service/io.pressure /sys/fs/cgroup/system.slice/<name>.service/io.statPSI IO stalls plus rbytes/wbytes/rios per major:minor. Helps find noisy disk neighbors
-
cat /sys/fs/cgroup/system.slice/<name>.service/cgroup.procs; systemctl status <name>.service | grep CGroupAll PIDs that are in the service cgroup right now. Compare them with the tree from systemctl status
-
systemd-cgls --all --no-pager; systemd-cgtop -d 2 --depth=3cgls --all also shows empty cgroups. cgtop ranks slices by live CPU, memory and IO
-
cgcreate -g memory:/<name>; cgset -r memory.limit_in_bytes=512M <name>; cgexec -g memory:/<name> <command>A throwaway memory limit with libcgroup v1. Note: on the unified v2 hierarchy, use systemd-run --scope -p
-
cat /sys/fs/cgroup/system.slice/<name>.service/memory.current /sys/fs/cgroup/system.slice/<name>.service/memory.maxCurrent memory usage of a systemd service (page cache included) and its hard limit. If current is close to max, OOM is near