High CPU Usage
Identify and fix high CPU usage on your Cafora Minecraft server.
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.

Locate the file log
Under Files, double-click logs and locate latest.log. Check modification times. Preserve the relevant file before a restart replaces or rotates it.

Read the complete error context
Open the log in the editor and inspect the earliest relevant error and surrounding lines. Remove tokens, passwords and private player details before sharing. Do not diagnose from the last line alone.

Describe the request to support
Open a support ticket with the service or invoice ID and the requested action. For connection issues include time, error and MTR evidence. Never include passwords, tokens or card details.

Identifying High CPU
- Check CPU graphs in the Pterodactyl Panel
- Sustained usage near your plan's allocated CPU limit indicates a problem
- Brief spikes during world saves or player joins are normal
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).
Common Causes
Entity Overload
Too many entities (mobs, items, villagers) consuming tick time:
- Check entity counts with
/spark healthreport - Reduce mob caps in server configuration
- Clear dropped items periodically
Inefficient Plugins
- Run a Spark profile to identify heavy plugins
- Remove or replace plugins consuming excessive CPU
- Update all plugins to latest versions
World Generation
- Pre-generate your world to avoid runtime chunk generation
- Set a world border to prevent infinite exploration
- Lower view distance to reduce loaded chunks
Redstone Activity
- Identify laggy redstone contraptions
- Limit hopper minecarts and flying machines
- Use observers instead of repeaters for clocks
Solutions
Run /spark profiler --timeout 120 to capture CPU usage.
Analyze the report to identify the top CPU consumers.
Apply optimization settings.
If the issue persists, consider upgrading your plan.