Performance Guide
Complete performance optimization guide for Cafora Minecraft servers.
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.

Step 1: Choose the Right Software
Server software choice is the single biggest performance factor:
| Software | Performance | Best For |
|---|---|---|
| Paper | Excellent | Most servers (recommended) |
| Purpur | Excellent+ | Advanced configuration needs |
| Fabric + Lithium | Very Good | Modded servers |
| Spigot | Good | Legacy compatibility |
| Vanilla | Baseline | Pure vanilla experience |
| Forge | Baseline | Heavy modpacks |
Step 2: Configure Server Properties
view-distance=8
simulation-distance=6
max-players=20
network-compression-threshold=256Step 3: Optimize Entity Settings
Reduce entity processing load in server configuration files. See optimization config examples.
Step 4: Pre-Generate Your World
Use Chunky to generate all chunks within your world border before players explore. This prevents the single biggest source of runtime lag.
Step 5: Profile and Iterate
- Run Spark profiler during peak player count
- Identify the top CPU and memory consumers
- Optimize or replace problem plugins/mods
- Repeat until performance is stable
Performance Troubleshooting
| Symptom | Likely Cause | Solution |
|---|---|---|
| Low TPS | CPU bottleneck | Profile with Spark, optimize |
| OOM crashes | RAM limit exceeded | Reduce usage or upgrade plan |
| Chunk lag | Runtime generation | Pre-generate world |
| Join lag | Too many chunks loading | Reduce view distance |
| Periodic lag | GC pauses | Optimize JVM flags |
| Entity lag | Too many mobs/items | Reduce mob caps, clear items |