CAFORADocs
Resources

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.

Check the console
Check the console2026-11-11 · Current application interface · demonstration data · Open full-size image

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.

Enter a supported command
Enter a supported command2026-11-11 · Current application interface · demonstration data · Open full-size image

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.

Check the command response
Check the command response2026-11-11 · Current application interface · demonstration data · Open full-size image

Step 1: Choose the Right Software

Server software choice is the single biggest performance factor:

SoftwarePerformanceBest For
PaperExcellentMost servers (recommended)
PurpurExcellent+Advanced configuration needs
Fabric + LithiumVery GoodModded servers
SpigotGoodLegacy compatibility
VanillaBaselinePure vanilla experience
ForgeBaselineHeavy modpacks

Step 2: Configure Server Properties

view-distance=8
simulation-distance=6
max-players=20
network-compression-threshold=256

Step 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

SymptomLikely CauseSolution
Low TPSCPU bottleneckProfile with Spark, optimize
OOM crashesRAM limit exceededReduce usage or upgrade plan
Chunk lagRuntime generationPre-generate world
Join lagToo many chunks loadingReduce view distance
Periodic lagGC pausesOptimize JVM flags
Entity lagToo many mobs/itemsReduce mob caps, clear items

See Also


Service information · Backups · Support

On this page