CAFORADocs
Performance

RAM & Memory

Manage and optimize memory usage for 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.

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

Separate container memory from the Java heap

Open Console, note the incident time and workload, and inspect the memory chart. Panel reports container resources; the Java heap is only part of process memory. The readings are not interchangeable.

MeasurementUse
Panel usage and service allowanceCheck proximity to the container limit
Heap trend after collectionInvestigate pressure alongside GC and spark reports
Startup memory settingsCheck that the heap budget leaves room for other process memory

Chunks, entities, plugins and mods have workload-dependent costs. There is no universal fixed cost per chunk, and world size on disk is not a measurement of current RAM use.

Record before changing

  • Preserve logs and identify whether spikes coincide with travel, chunk generation or player joins.
  • Compare similar workloads. A temporary rise before collection is not proof of a leak.
  • Check JVM and heap budgeting and collect evidence with spark.
  • Change one identified factor at a time, then check startup, memory and gameplay.

For a Java error or sudden termination, follow OOM troubleshooting. A chart approaching its limit alone is not a reason for repeated restarts or an immediate plan change.


Service information · Backups · Support

On this page