How to Read Minecraft Timings Report

Timings reports are performance summaries used by many Bukkit, Spigot, Paper, and forked servers. They can show expensive plugin tasks, world ticks, entity sections, and scheduler work, but they are easy to misread.

#Timings vs Spark

| Tool | Best for | Limitation | | --- | --- | --- | | Timings | Quick plugin and tick-section overview | Less detail than a profiler | | Spark profiler | Method-level performance investigation | Requires reading flame graphs or trees | | Logs | Startup errors and recurring warnings | Not a tick profiler |

On modern Paper, prefer Spark profiling for serious lag. Use timings when your host panel exposes it, when a plugin author asks for it, or when you need a quick overview.

#Capture the Right Window

Bad report: timings recorded while the server is empty.

Useful report: timings recorded while TPS is low, players are active, farms are loaded, and the problem is visible.

Before recording, note:

1. Player count.
2. Worlds loaded.
3. What players were doing.
4. Whether new chunks were generating.
5. Whether backups, saves, or restarts happened.

#What to Look At First

Start with the top expensive entries, but do not stop there.

| Report area | What it can reveal | | --- | --- | | Plugin tasks | Repeating jobs, database checks, scoreboard updates | | World tick | Entities, chunks, block entities, tile entities | | Scheduler | Plugins running work every tick | | Events | Plugins reacting to movement, chat, combat, block changes | | Commands | Command blocks, scripted plugins, automation |

If one plugin has a high percentage, ask what it was doing. A protection plugin may look expensive during mass block edits. An economy plugin may spike during database stalls. A scoreboard plugin may cost too much because it updates every player every tick.

#Avoid Common Misreads

Do not assume the largest line is automatically the root cause. Sometimes a plugin is shown because another plugin calls into it. Sometimes the expensive area is a world system, not a plugin.

Also watch for sample size. A tiny report can make one short spike look dominant. A very long report can average away the exact moment that hurt players.

#Turn Findings Into Action

Use timings to create a short suspect list:

1. Disable or reconfigure one suspect on a staging copy.
2. Reduce update frequency for scoreboards, holograms, maps, and menus.
3. Check plugin storage paths and database latency.
4. Compare with Spark when timings are vague.
5. Keep notes so you can revert changes that do not help.

For plugin-heavy servers, continue with how to find laggy plugins.