How to optimise your Fabric Minecraft server

Optimising a Fabric server ensures a smoother experience for your players by reducing lag and improving tick times. Follow these steps to get the best performance from your instance.

Install performance-enhancing mods

Fabric relies on community-made mods to optimise server performance. The most effective mods include Lithium (for game logic optimisation) and FerriteCore (for memory usage reduction).

On AwakeNode

Use the Mod Installer in your panel. Search for 'Lithium' or 'FerriteCore', click install, and restart your server. The panel handles the file placement automatically.

On other hosts

Download the correct versions of the mods from Modrinth or CurseForge. Use your SFTP client to upload the .jar files into the /mods directory in your server root, then restart the server.

Manage your world files

Large, unoptimised worlds can cause significant performance overhead. Regularly pruning unused chunks or using a world border can prevent your server from working harder than necessary.

On AwakeNode

Use the File Manager to locate your world folder. You can upload pre-generated world files or delete corrupted regions directly through the browser interface.

On other hosts

Connect via SFTP to access your server files. You will need to manually delete region files or use external tools to trim your world data.

Review your RAM allocation

If your server is consistently hitting high memory usage, it may cause 'lag spikes' as the Java Garbage Collector works harder to free up space.

On AwakeNode

If you require more RAM, simply upgrade your plan via the client area. The Xmx value updates automatically to match your new plan without any manual configuration required.

On other hosts

Locate your startup script or panel settings. You must manually edit the -Xmx flag (e.g., -Xmx4G for 4GB of RAM) to match your server's allocated memory.

Contact support for advanced tuning

Sometimes, performance issues require adjustments to JVM startup flags or Garbage Collection settings.

On AwakeNode

Clients cannot edit startup flags directly. If you believe your server requires custom JVM arguments, open a ticket with our Support team, and we will configure them for you.

On other hosts

You will need to manually add these arguments to your startup command line in your control panel or shell script.