Direct answer

A recurring lag interval often points to periodic work: autosaves, backups, plugin schedules, garbage collection or host-level contention.

Identify the failing layer

A regular timing pattern is evidence worth comparing to scheduled work; it does not identify the guilty task by itself.

First checks and evidence

  • Log the clock time of several spikes and find the repeating interval.
  • Capture a spark profile during at least one spike and note whether the main tick thread or a different resource is blocked.

Admin diagnosis and repair

  1. Compare timestamps with backup jobs, disk usage, GC records and plugin scheduled tasks.
  2. Move or optimize the identified job in staging; test before disabling safety-critical world saves or backups.

Verify the fix: Confirm spike frequency and duration decrease over several scheduled cycles without losing backup or save coverage.

Important safety note

Do not assume a recurring spike is GC just because heap usage changes; correlation with actual pause times is required.

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