Find out what is lagging your server.
Paste a spark link. You get a plain-English answer naming the plugin, the cost, and the fix, not a flame graph.
Three Things to Read, in Order
The result screen is built for a worried server owner first and an experienced admin second. Read the top, act on the middle, and only go to the bottom if you want to argue with it.
The verdict
One sentence, one colour. Critical means ticks are being dropped right now. Degraded means the server is holding but the next spike is already visible. Healthy means nothing in this capture is causing lag.
The findings
Each one carries the claim, the numbers that prove it, the plugin or mod it is attributed to, and a fix. Work top to bottom; a critical finding usually explains the warnings under it.
The cost table
Where the server thread spent its time, by plugin or mod. Time inside a plugin includes whatever it called into the game, which is why one add-on can reach a third of a tick.
Four Rules for a Profile Worth Reading
The analyzer is only as good as the capture. These four habits separate a report that names the problem from one that shrugs.
Profile while it lags
A profile of a quiet server tells you nothing. Start the profiler when players are complaining, not after.
Give it three minutes
Anything under a minute can miss autosave, periodic plugin work and the spawn cycle. Three minutes catches all of them.
Chase spikes separately
If the server is fine except for freezes, run /spark profiler start --only-ticks-over 100 so only the slow ticks are sampled.
Change one thing, then re-run
Update the plugin the analyzer named, profile again, compare. Two reports a week apart are worth more than one perfect one.
Frequently Asked Questions
What the analyzer reads, what it does with your report, and what to do when it names a plugin.
