Manage CPU/RAM per server

In a GameBox, every instance shares the same CPU and RAM pool. Distributing these resources properly prevents a hungry server from dragging the others down.

Cause / The problem

A server that eats all the available CPU or RAM makes the whole pool lag, and can even crash neighbouring instances by starving them of memory (OOM). The classic symptom: everything slows down as soon as a game starts or under a load spike.

Solution

1. Read the actual usage in the panel: Dashboard → your GameBox → Resources tab. You see the total RAM, per-instance usage and the remainder.
2. Set a RAM limit per instance at creation (or via Settings → Startup / Limits, depending on the panel). For Minecraft this is the -Xmx (Java heap); for other games, a soft limit.
3. Keep a safety margin: do not hand out 100% of the pool. Leave 10 to 20% for the system, the OS and spikes.
4. Watch the CPU: a core pinned at 100% by a game signals saturation. Throttle that server or reduce its tickrate / view distance.
5. Identify the culprit server by comparing usage before/after stopping each instance. The panel shows CPU/RAM consumption per server.
6. Resize the saturating server down: cut its allocated RAM, the number of slots, or the view distance, until usage is healthy again.
7. Resize an under-fed server up by reclaiming RAM freed by another server you stop or delete.

Best practice: one heavy server per GameBox, or several small well-balanced ones. Do not stack multiple heavy games if the RAM headroom is tight.