CAFORADocs
Performance

Storage Performance

Managing disk space and storage performance on 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

Storage Allocation

Storage type and capacity depend on your plan. The captured MY-L catalogue describes HDD RAID; confirm the live specification rather than assuming SSD storage. Disk usage includes:

  • World files (overworld, nether, end)
  • Plugin and mod data
  • Server logs
  • Backups (automatic and manual)
  • Configuration files

Monitoring Storage

View storage usage in the Pterodactyl Panel. The resource panel shows current disk usage and available space.

Managing Storage

Free Up Space

  • Delete old backups you no longer need
  • Remove unused worlds
  • Clear large log files
  • Trim plugin data stores

Optimize World Saves

  • Set a world border to prevent unlimited expansion
  • If pruning is necessary, use an explicitly supported pruning tool on a backup and test the result first
  • Convert worlds to optimized formats when available

Storage and Performance

Regardless of the storage type, concurrent I/O can affect performance:

  • Large autosaves can cause brief lag spikes
  • Generating new terrain writes chunks to disk
  • Many simultaneous chunk loads increase I/O

Service information · Backups · Support

On this page