Node capacity
How much memory and disk the game node has, has promised to servers, and is using.
About this page
Three numbers that are routinely different: what’s committed to servers, what’s actually used, and what physically exists. The gap between them is where outages come from.
Critical
{{ warn.text }}
{{ warn.pct }}
{{ memGap.badge }}{{ memGap.why }}
{{ node.memTitle }}
{{ node.sub }}Committed — sum of server limits (overcommit is the hatched zone)
{{ node.committedLabel }}{{ node.scaleLabel }}
Actually used — right now
Committed beyond what exists — an allocation problem: lower limits or move a server. Fix in Pterodactyl.
Using more than expected — a behaviour problem: a server near 100% of its own limit will OOM inside its container before the node notices.
{{ tableGap.badge }}{{ tableGap.why }}
Server
State
Limit
Used
Of its limit
Of physical
{{ r.name }}
{{ r.state }}
{{ r.limit }}
{{ r.used }}
{{ r.pct }}
{{ r.phys }}
{{ diskGap.badge }}{{ diskGap.why }}
{{ node.diskTitle }}
{{ node.diskSub }}{{ node.diskSummary }}
node02 · planned
HP EliteDesk 705 G4Moving modded (6,144 MB) here drops node01 to 63% committed — the single move that ends the overallocation.