Linux Server / Performance, Capacity & Containers
Check a service's cgroup limits when the host has spare capacity
A service can be throttled or memory-limited while the host looks healthy. Inspect unit-level resource properties.
Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
systemctl show app.service -p ControlGroup -p MemoryCurrent -p MemoryMax -p CPUQuotaPerSecUSecRead the result
On a supporting systemd and cgroup setup, these show configured limits and current accounting. Parent-slice constraints can impose additional effective limits.
Resolve and verify
Compare the service and parent hierarchy with approved resource policy, then correlate throttling or memory events with latency. Make a justified targeted adjustment and retest.
Before changing production
Do not remove all resource controls or assume a generous service limit overrides a tighter parent slice.