Resources

Set CPU and memory limits for your apps. This prevents one app from consuming all server resources.

Setting Resource Limits

Resource limits are configured through the Plitho dashboard, not plitho.yml.

1. Go to Apps → your app → Resources tab
2. Set CPU and memory limits
3. Save

How Limits Work

Field	Type	Description
CPU	float	CPU quota as cores (e.g., 0.5 = half core, 2.0 = 2 cores)
Memory Max	string	Hard limit — process is killed if exceeded
Memory High	string	Soft throttle — triggers reclaim before hitting max

Memory Formats

• 256M — 256 megabytes
• 1G — 1 gigabyte
• 512K — 512 kilobytes

CPU Values

• 0.5 — 50% of one core
• 1.0 — one full core
• 2.0 — two cores
• 4.0 — four cores

How Limits Are Enforced

Resource limits use systemd slices:

• CPU: CPUQuota — the process is throttled when it exceeds the quota
• Memory (max): MemoryMax — the process is killed if it exceeds this
• Memory (high): MemoryHigh — triggers memory reclaim before hitting max

Viewing Resource Usage

Go to Resources in the dashboard to see:

• Live CPU and memory usage per app
• Historical charts (1 hour to 30 days)
• Per-app allocation table with limits

How Resource Limits Are Calculated

When you set limits for an app, they count against your user quota. Your server administrator sets the total resources available to you. Plitho checks that the sum of all your apps' limits doesn't exceed your quota.

If you try to set limits that exceed your quota, the request is rejected.

Best Practices

• Start conservative (0.5 CPU, 256M memory) and increase based on actual usage
• Use memory_high as a warning threshold — it triggers reclaim before killing
• Monitor the Resources page to see actual usage patterns
• Always set limits in production — unlimited resources risk starving other apps

Tip

If you don't set any limits, your app runs with unlimited CPU and memory. Fine for development, not recommended for production.