Direct answer
Judge startup speed separately from in-game tick performance. Long startup times often reflect plugin initialization, world loading or first-run data conversion; fast startup does not prove the server can sustain player load.
Recommended procedure
- Record the time from launching Java until the server reports readiness and note whether it is the first run after an update.
- Read startup logs for the step taking time: plugin enabling, registry loading, world preparation or network/service connections.
- Compare a second clean restart without changing data; first-run migrations or cache creation can make the initial run unusually slow.
- Do not delete world folders to solve slow startup; isolate optional plugins on a copy if a plugin appears responsible.
- Once online, run a separate spark sample during real player activity to check runtime performance.
Why this matters
Startup includes operations that do not repeat every tick. A slower first run may be expected after significant version or plugin changes, but repeated hangs at the same log line deserve focused investigation.
Practical example: Example: the first start after moving a large world may spend extra time preparing or converting data; a later restart can finish faster. If every restart hangs at the same plugin enable line, that is more diagnostic than the total elapsed time. Save that section of the console output before experimenting with settings.
How to verify the result
- Check for a successful ready message and a bound listening port.
- Confirm plugin features and world data are present after startup.
- Record subsequent restart times; review warnings or stalls rather than only the total seconds.
Version and compatibility notes
- Panel startup timers may include provisioning or container delays outside Minecraft.
- Do not treat the startup
Donemessage as evidence of low MSPT.
Official references
These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.