Skip to main content
First identify where the lag occurs. Server-side, connection, and client lag require different fixes.

Check server-side causes

  1. Read the console for repeated errors, watchdog warnings, or overloaded messages.
  2. Check whether the problem began after adding a plugin, mod, add-on, farm, redstone machine, or large group of entities.
  3. Review view-distance, simulation-distance, and entity-broadcast-range-percentage in server.properties.
  4. Test one change at a time and compare performance under similar player load.

Profile the server with spark

Use spark on compatible plugin server software to find expensive plugins, tasks, entities, and server threads.
1

Install spark

Install a compatible spark .jar by following Install Java plugins, then restart the server.
2

Start a profiler

Run the profiler during the lag you want to investigate.
3

Stop and open the report

Let it collect representative activity, then stop it.
Open the generated report link.
4

Read the result

Check TPS, milliseconds per tick, memory and garbage collection, then inspect the plugin, mod, world, or thread consuming the most processing time.
A spark report may contain server details. Review it before sharing the link publicly.

Server properties

Adjust view, simulation, and entity broadcast distances.

Pregenerate the world

Generate chunks before high-speed exploration.