Performance tuning

Minecraft is single-threaded for the main world tick. That means the slowest allocated CPU path — not the total core count — is what governs your TPS.

What "good" looks like

• TPS at or near 20.0.
• MSPT (milliseconds per tick) under 50ms.
• No "Can't keep up!" warnings in the console.

Common causes of bad TPS

• Too many entities. Item frames, item drops, hostile mobs in unloaded areas, animal farms. Cull aggressively.
• Heavy redstone. Auto-farms with thousands of components per chunk are the #1 TPS killer.
• Misbehaving mods/plugins. Use /spark profiler (Spark plugin) to find which one.
• Too many loaded chunks. Lower view-distance and simulation-distance in server.properties.

What we monitor

The panel shows live CPU, RAM, and disk usage for your workload. In-game TPS monitoring (and the alerting that goes with it) is on the roadmap but not yet wired up — for now, watch the console for "Can't keep up!" warnings or run /spark tps yourself.

When to size up

If you're consistently at low TPS even after optimization, you've outgrown your current size. Reach out via support and we'll help you migrate.