Diagnose problems of a Minecraft is not always easy, but there are a few simple tools that allow to identify quickly the origin of performances problems, the report system called "timings".
It allows you to get information about calculation cycles of the Minecraft server precisely, then identify a map or a plugin causing problems.
There are two methods to get a report, whether it's a Bukkit or Spigot/Cauldron/SpongeForge server.
Timings with Paper
Activate profiling with the following command: :
/timings on
/timings paste
Timings with Bukkit
First, enable the profiling of plugins in the bukkit.yml from the FTP (with an FTP client or the WebFTP of the panel). Edit the line :
plugin-profiling: true
/timings reset
/timings merged
http://paste.ubuntu.com
Then, you will see in the URL that you past get an ID. Copy it then enter the URL like:
http://timings.aikar.co/?url=ID
Timings with Spigot or Cauldron
First active the plugin profiling by modifying the bukkit.yml file on your FTP (with an FTP client or the WebFTP of the panel).
Edit the line: plugin-profiling: true
.
Then restart the server. Wait for a few minutes, when freezes get started, enter the command :
/timings reset
/timings paste
Timings with SpongeForge
First, stop the server from the panel then enable the verbose mode of the timings system by editing the config file config/sponge/global.conf and more particularly the following line of "timings" section :
verbose=true
/sponge timings report