Performance Overview
Understanding and optimizing your Cafora Minecraft server performance.
Illustrated procedure
Screenshots show the current application with demonstration data. Use your own service details; click an image to inspect it at full size.
Check the console
Open Essentials → Console. Check the current state, startup output and errors before making changes. Wait for Done or your software’s ready message before joining.

Enter a supported command
Use the command field beneath the console. Panel console commands normally omit the leading slash. This example uses the read-only command list; use commands supported by your core or plugin.

Check the command response
Press Enter once, then read the response in the console. Confirm the target and effect before sending an administrative command. Example output is not a performance measurement.

Key Performance Metrics
| Metric | What It Measures | Good Range |
|---|---|---|
| TPS | Ticks per second (server update rate) | 19.8 - 20.0 |
| MSPT | Milliseconds per tick (time per update) | < 50 ms |
| CPU Usage | Processor utilization | Below 80% of plan limit |
| RAM Usage | Memory consumption | Below plan limit |
| Disk I/O | Storage read/write speeds | Varies by plan |
CPU usage is measured against a single thread: 100% means one thread (core) fully used. If your plan allocates multiple threads, usage can exceed 100% (e.g. 200% means two threads fully used).
Performance Goals
For a smooth Minecraft experience:
- 20 TPS is the ideal; below 18 and players notice lag
- MSPT under 50ms ensures the server keeps up with the tick rate
- Stable RAM usage prevents crashes and lag spikes
- Low disk latency matters for world saves and chunk generation
Quick Performance Checklist
If your server feels slow:
- View resource graphs in the Pterodactyl Panel
- Run a Spark profiler report
- Check TPS with
/tpscommand (Paper/Purpur) - Review optimization tips