BlackSpigot

Guide Capture useful server-lag evidence with spark before changing settings

  • Thread starter Thread starter BlackSpigot Guides
  • Start date Start date
B

BlackSpigot Guides

Guest
Goal: capture the slowdown while it happens and make one measurable change.

On Paper 1.21 and later, spark is bundled. With the appropriate server permission, start a ten-minute profile during the affected gameplay:
Code:
/spark profiler start --timeout 600

Record the time, player count, world and action that felt slow. Distinguish a delayed server action from low client frame rate or a poor network connection; they need different evidence.

When spark returns the report link, check which work dominates the affected period. Expand expensive branches instead of blaming whichever plugin happens to appear first. Note whether the workload involved normal play, exploration, startup or a scheduled task.

Keep the report and the original configuration. Test one change on a backup or during a planned maintenance window. Repeat under similar conditions and compare the same symptom. Restore the original setting if it makes things worse.

For help here, include the report, server build, plugin versions and reproduction steps. Review the report for information you do not want to publish before sharing it.

Profiler reference
 
Top