Direct answer

Saving may create short tick delays or storage saturation. Separate normal world-save activity from disk I/O stalls and plugins that write large files.

Identify the failing layer

The write path may involve world files, plugin databases and backup jobs with different resource costs.

First checks and evidence

  • Record the exact time and duration of freezes, and check whether they coincide with saves or backup rotation.
  • Inspect disk free space and I/O wait together with server MSPT and console messages.

Admin diagnosis and repair

  1. Check plugin databases and world backups for competing write-heavy operations at those timestamps.
  2. Test moving verified backups off-peak or improving storage contention; do not disable world saving to hide symptoms.

Verify the fix: Repeat the same save/backup cycle while measuring peak MSPT and verify all world and plugin data persist after graceful stop.

Important safety note

An apparently fast SSD can still stall under shared-host contention or nearly full storage. Use measurements rather than vendor labels alone.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000