You decide which services we may enable for analytics, personalization, and external content.
We use cookies and similar technologies on our website to personalize content, embed external media, and better understand how individual areas are used.
Necessary cookies
These entries support essential functions such as security, stability, and form processing.
Optional sections
AnalyticsMarketingPersonalizationExternal media
Your data may be processed with your consent or on the basis of legitimate interests. In the cookie settings, you can reject or explicitly allow each optional category.
Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.
You can reopen and change your selection at any time. · 1.0.2
Minecraft: Detect Server Issues with Timings Report
Discover how to analyze server performance issues with timings reports to identify lags and optimize your server → Learn more now
10 November 20263 min read0 Views0 helpful
Explanation
What is a Timings Report?
Timings reports are similar to your PC’s Task Manager and help you find issues, especially lag. A timings report records all server activities and displays them visually.
FAQ
Frequently asked questions
A timings report is like your PC’s Task Manager and helps you find issues, especially lag, by recording and visually displaying all server activities.
Start recording with the command /timings start (except on Paper Spigot if unchanged). Use the server normally during recording for at least 10 minutes.
Use the command /timings paste. After a few seconds, a success message with a link will appear to open the report.
Feedback
Was this article helpful?
Your feedback helps us prioritize and improve content.
0 of 0 Users found this article helpful.
Personal support
Need more help than the guide provides?
Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.
Navigation
Minecraft
Creating a Timings Report
Depending on your server software, the timings report is created differently. Basically, you need to start the recording first with the following command (except for Paper Spigot if settings are unchanged):
/timings start
While recording, use the server as usual so that any issues can be captured and later analyzed in detail. The recording should last at least 10 minutes or longer if possible.
Exporting the Timings Report
To create and export the timings report, use this command:
/timings paste
After a few seconds, a message will appear confirming the export was successful. You can open the timings report via the provided link.
Analysis
↔️ Narrowing Down Values
Once the timings report is exported and opened as described above, a window similar to this should appear:
First, examine the graph closely to check rough values at different recording points by hovering your mouse over the points.
To get the most accurate values indicating a possible server problem, narrow down the problematic time frame using the sliders below, as shown in the graph:
Investigating Server Values
There are three columns in total. As shown in the screenshot below, box number 1 shows what percentage of a tick (20 ticks equal one second) the main process requires. You also see how often this process ran during the recording.
Box number 2 provides more precise values in milliseconds, but note that the time should never exceed 50ms. If it does, this triggers a chain reaction causing all other processes to backlog, ultimately leading to lag because the server can only process tasks with delay.
Info
The Full Server Tick can usually be ignored since its values are always in the red zone, which is not a major problem.
You should definitely take a closer look at the color-highlighted values.
In this example, we look at the process for all entities (animals, monsters, items, etc.) since the values are already marked orange. This directly indicates a problem with too many entities on the server.
Maybe there are mob farms or massive mob spawning. If you have issues with too many entities, you can reduce spawn rates in settings or install plugins that limit entity counts and automatically remove them if needed.
As described above, the list generally always shows the main process. By clicking on a process, you can examine individual processes for each entity type in more detail. Also pay attention to columns 2 and 3 as mentioned earlier.
You will see that Minecraft::tickEntity - nms.EntitySkeleton executed many processes. Mob farms could be the cause here as well.
Another process with orange values is waiting blocks. Waiting blocks can be especially inefficient because the server must check the status of each waiting block every tick. Examples include falling sand, gravel, lava, and water.
For example, if a lot of water is used on a large farm, it can cause many problems. This issue can also occur when new chunks generate and water sources form in mountains within those chunks. The server must recalculate the status each time for the water to flow. Additionally, the server must create and load chunks, which is also a very intensive process.
You can perform all other investigations similarly, as the steps are identical for every other process. If you still need help interpreting the data, we are always here for you!
Checking Plugins
Sometimes problems are caused by plugins. To find out if a plugin is the culprit, you can temporarily remove plugins from the server and check the current state again.
If there is a plugin issue, you can also investigate it in the “Plugins” section. The values are also listed in three columns with the same structure as the normal server values above. The difference is that no main process is shown here, but the plugin itself. Still, you can open all processes by clicking and examine the values in detail.
Server hosting from €2.49 / month, online instantly, DDoS protection included.
Preferred source on Google
