CAFORADocs
Performance

JVM & Garbage Collection

Optimize Java Virtual Machine settings for your Cafora 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

Start with the effective template configuration

Open Configuration & records → Startup and record the Java image, command and editable variables. Match the runtime to the server and mod versions. Contact support when the template locks the command.

Budget the heap within the service allowance

-Xms sets the initial heap and -Xmx the maximum heap. Thread stacks, class metadata and direct buffers also need memory outside it. Do not assign the entire container allowance to -Xmx.

Record the current settings and allowance, then evaluate workload, GC and process measurements. This guide supplies neither a fixed 10G command nor a universal headroom percentage. Decide whether initial and maximum heaps should match for the actual environment.

Change and roll back

  • Save the original command and variables. Confirm compatibility with the installed Java version.
  • Arrange maintenance and change one related group of settings at a time. Stop normally before starting again.
  • Check startup and subsequent load. Restore the original settings after a failure instead of stacking more flags.
  • Ask support with logs when collector compatibility or template permissions are unclear.

Do not choose G1 or ZGC solely from memory capacity. Start from the validated template and consult Paper’s flag reference together with the installed Java documentation.

Related: startup and server selection, GC diagnosis, OOM troubleshooting.


Service information · Backups · Support

On this page